Uplink transmission in new radio unlicensed band

ABSTRACT

A wireless device receives configuration parameters of a bandwidth part comprising resource block (RB) sets, wherein control channel elements (CCEs) are across the RB sets and a subset of the CCEs, within each RB set of the RB sets, are indexed from a same initial value. Control information is received via one or more CCEs of a first subset, of the CCEs, within an RB set of the RB sets. The wireless device transmits a signal via an uplink resource based on an index of a CCE of the one or more CCEs.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of International Application No.PCT/US2020/058814, filed Nov. 4, 2020, which claims the benefit of U.S.Provisional Application No. 62/930,130, filed Nov. 4, 2019, the contentsof each of which are hereby incorporated by reference in theirentireties.

BRIEF DESCRIPTION OF THE DRAWINGS

Examples of several of the various embodiments of the present disclosureare described herein with reference to the drawings.

FIG. 1A and FIG. 1B illustrate example mobile communication networks inwhich embodiments of the present disclosure may be implemented.

FIG. 2A and FIG. 2B respectively illustrate a New Radio (NR) user planeand control plane protocol stack.

FIG. 3 illustrates an example of services provided between protocollayers of the NR user plane protocol stack of FIG. 2A.

FIG. 4A illustrates an example downlink data flow through the NR userplane protocol stack of FIG. 2A.

FIG. 4B illustrates an example format of a MAC subheader in a MAC PDU.

FIG. 5A and FIG. 5B respectively illustrate a mapping between logicalchannels, transport channels, and physical channels for the downlink anduplink.

FIG. 6 is an example diagram showing RRC state transitions of a UE.

FIG. 7 illustrates an example configuration of an NR frame into whichOFDM symbols are grouped.

FIG. 8 illustrates an example configuration of a slot in the time andfrequency domain for an NR carrier.

FIG. 9 illustrates an example of bandwidth adaptation using threeconfigured BWPs for an NR carrier.

FIG. 10A illustrates three carrier aggregation configurations with twocomponent carriers.

FIG. 10B illustrates an example of how aggregated cells may beconfigured into one or more PUCCH groups.

FIG. 11A illustrates an example of an SS/PBCH block structure andlocation.

FIG. 11B illustrates an example of CSI-RSs that are mapped in the timeand frequency domains.

FIG. 12A and FIG. 12B respectively illustrate examples of three downlinkand uplink beam management procedures.

FIG. 13A, FIG. 13B, and FIG. 13C respectively illustrate a four-stepcontention-based random access procedure, a two-step contention-freerandom access procedure, and another two-step random access procedure.

FIG. 14A illustrates an example of CORESET configurations for abandwidth part.

FIG. 14B illustrates an example of a CCE-to-REG mapping for DCItransmission on a CORESET and PDCCH processing.

FIG. 15 illustrates an example of a wireless device in communicationwith a base station.

FIG. 16A, FIG. 16B, FIG. 16C, and FIG. 16D illustrate example structuresfor uplink and downlink transmission.

FIG. 17A, FIG. 17B and FIG. 17C show examples of MAC subheaders.

FIG. 18A shows an example of a DL MAC PDU.

FIG. 18B shows an example of an UL MAC PDU.

FIG. 19 shows an example of multiple LCIDs of downlink as per an aspectof an example embodiment of the disclosure.

FIG. 20 shows an example of multiple LCIDs of uplink as per an aspect ofan example embodiment of the disclosure.

FIG. 21A and FIG. 21B show examples of SCell activation/deactivation MACCEs as per an aspect of an example embodiment of the disclosure.

FIG. 22 shows an example of BWP management as per an aspect of anexample embodiment of the disclosure.

FIG. 23 shows an example of search space configuration as per an aspectof an example embodiment of the disclosure.

FIG. 24 shows an example of control resource set configuration as per anaspect of an example embodiment of the disclosure.

FIG. 25A is a flowchart of downlink transport block delivery as per anaspect of an example embodiment of the disclosure.

FIG. 25B shows an example of PUCCH resource determination as per anaspect of an example embodiment of the disclosure.

FIG. 26 shows an example of PUCCH resource indication as per an aspectof an example embodiment of the disclosure.

FIG. 27A shows an example of control resource set (CORESET)configuration as per an aspect of an example embodiment of thedisclosure.

FIG. 27B shows an example of CORESET configuration in a NR-U system asper an aspect of an example embodiment of the disclosure.

FIG. 28 shows an example of PUCCH resource selection as per an aspect ofan example embodiment of the disclosure.

FIG. 29 shows an example of PUCCH resource selection as per an aspect ofan example embodiment of the disclosure.

FIG. 30 shows an example of PUCCH resource selection as per an aspect ofan example embodiment of the disclosure.

FIG. 31 shows an example of PUCCH resource selection as per an aspect ofan example embodiment of the disclosure.

FIG. 32 is a flowchart of PUCCH resource selection as per an aspect ofan example embodiment of the disclosure.

FIG. 33 is a flowchart of PUCCH resource selection as per an aspect ofan example embodiment of the disclosure.

FIG. 34 is a flowchart of PUCCH resource selection as per an aspect ofan example embodiment of the disclosure.

DETAILED DESCRIPTION

In the present disclosure, various embodiments are presented as examplesof how the disclosed techniques may be implemented and/or how thedisclosed techniques may be practiced in environments and scenarios. Itwill be apparent to persons skilled in the relevant art that variouschanges in form and detail can be made therein without departing fromthe scope. In fact, after reading the description, it will be apparentto one skilled in the relevant art how to implement alternativeembodiments. The present embodiments should not be limited by any of thedescribed exemplary embodiments. The embodiments of the presentdisclosure will be described with reference to the accompanyingdrawings. Limitations, features, and/or elements from the disclosedexample embodiments may be combined to create further embodiments withinthe scope of the disclosure. Any figures which highlight thefunctionality and advantages, are presented for example purposes only.The disclosed architecture is sufficiently flexible and configurable,such that it may be utilized in ways other than that shown. For example,the actions listed in any flowchart may be re-ordered or only optionallyused in some embodiments.

Embodiments may be configured to operate as needed. The disclosedmechanism may be performed when certain criteria are met, for example,in a wireless device, a base station, a radio environment, a network, acombination of the above, and/or the like. Example criteria may bebased, at least in part, on for example, wireless device or network nodeconfigurations, traffic load, initial system set up, packet sizes,traffic characteristics, a combination of the above, and/or the like.When the one or more criteria are met, various example embodiments maybe applied. Therefore, it may be possible to implement exampleembodiments that selectively implement disclosed protocols.

A base station may communicate with a mix of wireless devices. Wirelessdevices and/or base stations may support multiple technologies, and/ormultiple releases of the same technology. Wireless devices may have somespecific capability(ies) depending on wireless device category and/orcapability(ies). When this disclosure refers to a base stationcommunicating with a plurality of wireless devices, this disclosure mayrefer to a subset of the total wireless devices in a coverage area. Thisdisclosure may refer to, for example, a plurality of wireless devices ofa given LTE or 5G release with a given capability and in a given sectorof the base station. The plurality of wireless devices in thisdisclosure may refer to a selected plurality of wireless devices, and/ora subset of total wireless devices in a coverage area which performaccording to disclosed methods, and/or the like. There may be aplurality of base stations or a plurality of wireless devices in acoverage area that may not comply with the disclosed methods, forexample, those wireless devices or base stations may perform based onolder releases of LTE or 5G technology.

In this disclosure, “a” and “an” and similar phrases are to beinterpreted as “at least one” and “one or more.” Similarly, any termthat ends with the suffix “(s)” is to be interpreted as “at least one”and “one or more.” In this disclosure, the term “may” is to beinterpreted as “may, for example.” In other words, the term “may” isindicative that the phrase following the term “may” is an example of oneof a multitude of suitable possibilities that may, or may not, beemployed by one or more of the various embodiments. The terms“comprises” and “consists of”, as used herein, enumerate one or morecomponents of the element being described. The term “comprises” isinterchangeable with “includes” and does not exclude unenumeratedcomponents from being included in the element being described. Bycontrast, “consists of” provides a complete enumeration of the one ormore components of the element being described. The term “based on”, asused herein, should be interpreted as “based at least in part on” ratherthan, for example, “based solely on”. The term “and/or” as used hereinrepresents any possible combination of enumerated elements. For example,“A, B, and/or C” may represent A; B; C; A and B; A and C; B and C; or A,B, and C.

If A and B are sets and every element of A is an element of B, A iscalled a subset of B. In this specification, only non-empty sets andsubsets are considered. For example, possible subsets of B={cell1,cell2} are: {cell1}, {cell2}, and {cell1, cell2}. The phrase “based on”(or equally “based at least on”) is indicative that the phrase followingthe term “based on” is an example of one of a multitude of suitablepossibilities that may, or may not, be employed to one or more of thevarious embodiments. The phrase “in response to” (or equally “inresponse at least to”) is indicative that the phrase following thephrase “in response to” is an example of one of a multitude of suitablepossibilities that may, or may not, be employed to one or more of thevarious embodiments. The phrase “depending on” (or equally “depending atleast to”) is indicative that the phrase following the phrase “dependingon” is an example of one of a multitude of suitable possibilities thatmay, or may not, be employed to one or more of the various embodiments.The phrase “employing/using” (or equally “employing/using at least”) isindicative that the phrase following the phrase “employing/using” is anexample of one of a multitude of suitable possibilities that may, or maynot, be employed to one or more of the various embodiments.

The term configured may relate to the capacity of a device whether thedevice is in an operational or non-operational state. Configured mayrefer to specific settings in a device that effect the operationalcharacteristics of the device whether the device is in an operational ornon-operational state. In other words, the hardware, software, firmware,registers, memory values, and/or the like may be “configured” within adevice, whether the device is in an operational or nonoperational state,to provide the device with specific characteristics. Terms such as “acontrol message to cause in a device” may mean that a control messagehas parameters that may be used to configure specific characteristics ormay be used to implement certain actions in the device, whether thedevice is in an operational or non-operational state.

In this disclosure, parameters (or equally called, fields, orInformation elements: IEs) may comprise one or more information objects,and an information object may comprise one or more other objects. Forexample, if parameter (IE) N comprises parameter (IE) M, and parameter(IE) M comprises parameter (IE) K, and parameter (IE) K comprisesparameter (information element) J. Then, for example, N comprises K, andN comprises J. In an example embodiment, when one or more messagescomprise a plurality of parameters, it implies that a parameter in theplurality of parameters is in at least one of the one or more messages,but does not have to be in each of the one or more messages.

Many features presented are described as being optional through the useof “may” or the use of parentheses. For the sake of brevity andlegibility, the present disclosure does not explicitly recite each andevery permutation that may be obtained by choosing from the set ofoptional features. The present disclosure is to be interpreted asexplicitly disclosing all such permutations. For example, a systemdescribed as having three optional features may be embodied in sevenways, namely with just one of the three possible features, with any twoof the three possible features or with three of the three possiblefeatures.

Many of the elements described in the disclosed embodiments may beimplemented as modules. A module is defined here as an element thatperforms a defined function and has a defined interface to otherelements. The modules described in this disclosure may be implemented inhardware, software in combination with hardware, firmware, wetware (e.g.hardware with a biological element) or a combination thereof, which maybe behaviorally equivalent. For example, modules may be implemented as asoftware routine written in a computer language configured to beexecuted by a hardware machine (such as C, C++, Fortran, Java, Basic,Matlab or the like) or a modeling/simulation program such as Simulink,Stateflow, GNU Octave, or Lab VIEWMathScript. It may be possible toimplement modules using physical hardware that incorporates discrete orprogrammable analog, digital and/or quantum hardware. Examples ofprogrammable hardware comprise: computers, microcontrollers,microprocessors, application-specific integrated circuits (ASICs); fieldprogrammable gate arrays (FPGAs); and complex programmable logic devices(CPLDs). Computers, microcontrollers and microprocessors are programmedusing languages such as assembly, C, C++ or the like. FPGAs, ASICs andCPLDs are often programmed using hardware description languages (HDL)such as VHSIC hardware description language (VHDL) or Verilog thatconfigure connections between internal hardware modules with lesserfunctionality on a programmable device. The mentioned technologies areoften used in combination to achieve the result of a functional module.

FIG. 1A illustrates an example of a mobile communication network 100 inwhich embodiments of the present disclosure may be implemented. Themobile communication network 100 may be, for example, a public landmobile network (PLMN) run by a network operator. As illustrated in FIG.1A, the mobile communication network 100 includes a core network (CN)102, a radio access network (RAN) 104, and a wireless device 106.

The CN 102 may provide the wireless device 106 with an interface to oneor more data networks (DNs), such as public DNs (e.g., the Internet),private DNs, and/or intra-operator DNs. As part of the interfacefunctionality, the CN 102 may set up end-to-end connections between thewireless device 106 and the one or more DNs, authenticate the wirelessdevice 106, and provide charging functionality.

The RAN 104 may connect the CN 102 to the wireless device 106 throughradio communications over an air interface. As part of the radiocommunications, the RAN 104 may provide scheduling, radio resourcemanagement, and retransmission protocols. The communication directionfrom the RAN 104 to the wireless device 106 over the air interface isknown as the downlink and the communication direction from the wirelessdevice 106 to the RAN 104 over the air interface is known as the uplink.Downlink transmissions may be separated from uplink transmissions usingfrequency division duplexing (FDD), time-division duplexing (TDD),and/or some combination of the two duplexing techniques.

The term wireless device may be used throughout this disclosure to referto and encompass any mobile device or fixed (non-mobile) device forwhich wireless communication is needed or usable. For example, awireless device may be a telephone, smart phone, tablet, computer,laptop, sensor, meter, wearable device, Internet of Things (IoT) device,vehicle roadside unit (RSU), relay node, automobile, and/or anycombination thereof. The term wireless device encompasses otherterminology, including user equipment (UE), user terminal (UT), accessterminal (AT), mobile station, handset, wireless transmit and receiveunit (WTRU), and/or wireless communication device.

The RAN 104 may include one or more base stations (not shown). The termbase station may be used throughout this disclosure to refer to andencompass a Node B (associated with UMTS and/or 3G standards), anEvolved Node B (eNB, associated with E-UTRA and/or 4G standards), aremote radio head (RRH), a baseband processing unit coupled to one ormore RRHs, a repeater node or relay node used to extend the coveragearea of a donor node, a Next Generation Evolved Node B (ng-eNB), aGeneration Node B (gNB, associated with NR and/or 5G standards), anaccess point (AP, associated with, for example, WiFi or any othersuitable wireless communication standard), and/or any combinationthereof. A base station may comprise at least one gNB Central Unit(gNB-CU) and at least one a gNB Distributed Unit (gNB-DU).

A base station included in the RAN 104 may include one or more sets ofantennas for communicating with the wireless device 106 over the airinterface. For example, one or more of the base stations may includethree sets of antennas to respectively control three cells (or sectors).The size of a cell may be determined by a range at which a receiver(e.g., a base station receiver) can successfully receive thetransmissions from a transmitter (e.g., a wireless device transmitter)operating in the cell. Together, the cells of the base stations mayprovide radio coverage to the wireless device 106 over a wide geographicarea to support wireless device mobility.

In addition to three-sector sites, other implementations of basestations are possible. For example, one or more of the base stations inthe RAN 104 may be implemented as a sectored site with more or less thanthree sectors. One or more of the base stations in the RAN 104 may beimplemented as an access point, as a baseband processing unit coupled toseveral remote radio heads (RRHs), and/or as a repeater or relay nodeused to extend the coverage area of a donor node. A baseband processingunit coupled to RRHs may be part of a centralized or cloud RANarchitecture, where the baseband processing unit may be eithercentralized in a pool of baseband processing units or virtualized. Arepeater node may amplify and rebroadcast a radio signal received from adonor node. A relay node may perform the same/similar functions as arepeater node but may decode the radio signal received from the donornode to remove noise before amplifying and rebroadcasting the radiosignal.

The RAN 104 may be deployed as a homogenous network of macrocell basestations that have similar antenna patterns and similar high-leveltransmit powers. The RAN 104 may be deployed as a heterogeneous network.In heterogeneous networks, small cell base stations may be used toprovide small coverage areas, for example, coverage areas that overlapwith the comparatively larger coverage areas provided by macrocell basestations. The small coverage areas may be provided in areas with highdata traffic (or so-called “hotspots”) or in areas with weak macrocellcoverage. Examples of small cell base stations include, in order ofdecreasing coverage area, microcell base stations, picocell basestations, and femtocell base stations or home base stations.

The Third-Generation Partnership Project (3GPP) was formed in 1998 toprovide global standardization of specifications for mobilecommunication networks similar to the mobile communication network 100in FIG. 1A. To date, 3GPP has produced specifications for threegenerations of mobile networks: a third generation (3G) network known asUniversal Mobile Telecommunications System (UMTS), a fourth generation(4G) network known as Long-Term Evolution (LTE), and a fifth generation(5G) network known as 5G System (5GS). Embodiments of the presentdisclosure are described with reference to the RAN of a 3GPP 5G network,referred to as next-generation RAN (NG-RAN). Embodiments may beapplicable to RANs of other mobile communication networks, such as theRAN 104 in FIG. 1A, the RANs of earlier 3G and 4G networks, and those offuture networks yet to be specified (e.g., a 3GPP 6G network). NG-RANimplements 5G radio access technology known as New Radio (NR) and may beprovisioned to implement 4G radio access technology or other radioaccess technologies, including non-3GPP radio access technologies.

FIG. 1B illustrates another example mobile communication network 150 inwhich embodiments of the present disclosure may be implemented. Mobilecommunication network 150 may be, for example, a PLMN run by a networkoperator. As illustrated in FIG. 1B, mobile communication network 150includes a 5G core network (5G-CN) 152, an NG-RAN 154, and UEs 156A and156B (collectively UEs 156). These components may be implemented andoperate in the same or similar manner as corresponding componentsdescribed with respect to FIG. 1A.

The 5G-CN 152 provides the UEs 156 with an interface to one or more DNs,such as public DNs (e.g., the Internet), private DNs, and/orintra-operator DNs. As part of the interface functionality, the 5G-CN152 may set up end-to-end connections between the UEs 156 and the one ormore DNs, authenticate the UEs 156, and provide charging functionality.Compared to the CN of a 3GPP 4G network, the basis of the 5G-CN 152 maybe a service-based architecture. This means that the architecture of thenodes making up the 5G-CN 152 may be defined as network functions thatoffer services via interfaces to other network functions. The networkfunctions of the 5G-CN 152 may be implemented in several ways, includingas network elements on dedicated or shared hardware, as softwareinstances running on dedicated or shared hardware, or as virtualizedfunctions instantiated on a platform (e.g., a cloud-based platform).

As illustrated in FIG. 1B, the 5G-CN 152 includes an Access and MobilityManagement Function (AMF) 158A and a User Plane Function (UPF) 158B,which are shown as one component AMF/UPF 158 in FIG. 1B for ease ofillustration. The UPF 158B may serve as a gateway between the NG-RAN 154and the one or more DNs. The UPF 158B may perform functions such aspacket routing and forwarding, packet inspection and user plane policyrule enforcement, traffic usage reporting, uplink classification tosupport routing of traffic flows to the one or more DNs, quality ofservice (QoS) handling for the user plane (e.g., packet filtering,gating, uplink/downlink rate enforcement, and uplink trafficverification), downlink packet buffering, and downlink data notificationtriggering. The UPF 158B may serve as an anchor point forintra-/inter-Radio Access Technology (RAT) mobility, an externalprotocol (or packet) data unit (PDU) session point of interconnect tothe one or more DNs, and/or a branching point to support a multi-homedPDU session. The UEs 156 may be configured to receive services through aPDU session, which is a logical connection between a UE and a DN.

The AMF 158A may perform functions such as Non-Access Stratum (NAS)signaling termination, NAS signaling security, Access Stratum (AS)security control, inter-CN node signaling for mobility between 3GPPaccess networks, idle mode UE reachability (e.g., control and executionof paging retransmission), registration area management, intra-systemand inter-system mobility support, access authentication, accessauthorization including checking of roaming rights, mobility managementcontrol (subscription and policies), network slicing support, and/orsession management function (SMF) selection. NAS may refer to thefunctionality operating between a CN and a UE, and AS may refer to thefunctionality operating between the UE and a RAN.

The 5G-CN 152 may include one or more additional network functions thatare not shown in FIG. 1B for the sake of clarity. For example, the 5G-CN152 may include one or more of a Session Management Function (SMF), anNR Repository Function (NRF), a Policy Control Function (PCF), a NetworkExposure Function (NEF), a Unified Data Management (UDM), an ApplicationFunction (AF), and/or an Authentication Server Function (AUSF).

The NG-RAN 154 may connect the 5G-CN 152 to the UEs 156 through radiocommunications over the air interface. The NG-RAN 154 may include one ormore gNBs, illustrated as gNB 160A and gNB 160B (collectively gNBs 160)and/or one or more ng-eNBs, illustrated as ng-eNB 162A and ng-eNB 162B(collectively ng-eNBs 162). The gNBs 160 and ng-eNBs 162 may be moregenerically referred to as base stations. The gNBs 160 and ng-eNBs 162may include one or more sets of antennas for communicating with the UEs156 over an air interface. For example, one or more of the gNBs 160and/or one or more of the ng-eNBs 162 may include three sets of antennasto respectively control three cells (or sectors). Together, the cells ofthe gNBs 160 and the ng-eNBs 162 may provide radio coverage to the UEs156 over a wide geographic area to support UE mobility.

As shown in FIG. 1B, the gNBs 160 and/or the ng-eNBs 162 may beconnected to the 5G-CN 152 by means of an NG interface and to other basestations by an Xn interface. The NG and Xn interfaces may be establishedusing direct physical connections and/or indirect connections over anunderlying transport network, such as an internet protocol (IP)transport network. The gNBs 160 and/or the ng-eNBs 162 may be connectedto the UEs 156 by means of a Uu interface. For example, as illustratedin FIG. 1B, gNB 160A may be connected to the UE 156A by means of a Uuinterface. The NG, Xn, and Uu interfaces are associated with a protocolstack. The protocol stacks associated with the interfaces may be used bythe network elements in FIG. 1B to exchange data and signaling messagesand may include two planes: a user plane and a control plane. The userplane may handle data of interest to a user. The control plane mayhandle signaling messages of interest to the network elements.

The gNBs 160 and/or the ng-eNBs 162 may be connected to one or moreAMF/UPF functions of the 5G-CN 152, such as the AMF/UPF 158, by means ofone or more NG interfaces. For example, the gNB 160A may be connected tothe UPF 158B of the AMF/UPF 158 by means of an NG-User plane (NG-U)interface. The NG-U interface may provide delivery (e.g., non-guaranteeddelivery) of user plane PDUs between the gNB 160A and the UPF 158B. ThegNB 160A may be connected to the AMF 158A by means of an NG-Controlplane (NG-C) interface. The NG-C interface may provide, for example, NGinterface management, UE context management, UE mobility management,transport of NAS messages, paging, PDU session management, andconfiguration transfer and/or warning message transmission.

The gNBs 160 may provide NR user plane and control plane protocolterminations towards the UEs 156 over the Uu interface. For example, thegNB 160A may provide NR user plane and control plane protocolterminations toward the UE 156A over a Uu interface associated with afirst protocol stack. The ng-eNBs 162 may provide Evolved UMTSTerrestrial Radio Access (E-UTRA) user plane and control plane protocolterminations towards the UEs 156 over a Uu interface, where E-UTRArefers to the 3GPP 4G radio-access technology. For example, the ng-eNB162B may provide E-UTRA user plane and control plane protocolterminations towards the UE 156B over a Uu interface associated with asecond protocol stack.

The 5G-CN 152 was described as being configured to handle NR and 4Gradio accesses. It will be appreciated by one of ordinary skill in theart that it may be possible for NR to connect to a 4G core network in amode known as “non-standalone operation.” In non-standalone operation, a4G core network is used to provide (or at least support) control-planefunctionality (e.g., initial access, mobility, and paging). Althoughonly one AMF/UPF 158 is shown in FIG. 1B, one gNB or ng-eNB may beconnected to multiple AMF/UPF nodes to provide redundancy and/or to loadshare across the multiple AMF/UPF nodes.

As discussed, an interface (e.g., Uu, Xn, and NG interfaces) between thenetwork elements in FIG. 1B may be associated with a protocol stack thatthe network elements use to exchange data and signaling messages. Aprotocol stack may include two planes: a user plane and a control plane.The user plane may handle data of interest to a user, and the controlplane may handle signaling messages of interest to the network elements.

FIG. 2A and FIG. 2B respectively illustrate examples of NR user planeand NR control plane protocol stacks for the Uu interface that liesbetween a UE 210 and a gNB 220. The protocol stacks illustrated in FIG.2A and FIG. 2B may be the same or similar to those used for the Uuinterface between, for example, the UE 156A and the gNB 160A shown inFIG. 1B.

FIG. 2A illustrates a NR user plane protocol stack comprising fivelayers implemented in the UE 210 and the gNB 220. At the bottom of theprotocol stack, physical layers (PHYs) 211 and 221 may provide transportservices to the higher layers of the protocol stack and may correspondto layer 1 of the Open Systems Interconnection (OSI) model. The nextfour protocols above PHYs 211 and 221 comprise media access controllayers (MACs) 212 and 222, radio link control layers (RLCs) 213 and 223,packet data convergence protocol layers (PDCPs) 214 and 224, and servicedata application protocol layers (SDAPs) 215 and 225. Together, thesefour protocols may make up layer 2, or the data link layer, of the OSImodel.

FIG. 3 illustrates an example of services provided between protocollayers of the NR user plane protocol stack. Starting from the top ofFIG. 2A and FIG. 3 , the SDAPs 215 and 225 may perform QoS flowhandling. The UE 210 may receive services through a PDU session, whichmay be a logical connection between the UE 210 and a DN. The PDU sessionmay have one or more QoS flows. A UPF of a CN (e.g., the UPF 158B) maymap IP packets to the one or more QoS flows of the PDU session based onQoS requirements (e.g., in terms of delay, data rate, and/or errorrate). The SDAPs 215 and 225 may perform mapping/de-mapping between theone or more QoS flows and one or more data radio bearers. Themapping/de-mapping between the QoS flows and the data radio bearers maybe determined by the SDAP 225 at the gNB 220. The SDAP 215 at the UE 210may be informed of the mapping between the QoS flows and the data radiobearers through reflective mapping or control signaling received fromthe gNB 220. For reflective mapping, the SDAP 225 at the gNB 220 maymark the downlink packets with a QoS flow indicator (QFI), which may beobserved by the SDAP 215 at the UE 210 to determine themapping/de-mapping between the QoS flows and the data radio bearers.

The PDCPs 214 and 224 may perform header compression/decompression toreduce the amount of data that needs to be transmitted over the airinterface, ciphering/deciphering to prevent unauthorized decoding ofdata transmitted over the air interface, and integrity protection (toensure control messages originate from intended sources. The PDCPs 214and 224 may perform retransmissions of undelivered packets, in-sequencedelivery and reordering of packets, and removal of packets received induplicate due to, for example, an intra-gNB handover. The PDCPs 214 and224 may perform packet duplication to improve the likelihood of thepacket being received and, at the receiver, remove any duplicatepackets. Packet duplication may be useful for services that require highreliability.

Although not shown in FIG. 3 , PDCPs 214 and 224 may performmapping/de-mapping between a split radio bearer and RLC channels in adual connectivity scenario. Dual connectivity is a technique that allowsa UE to connect to two cells or, more generally, two cell groups: amaster cell group (MCG) and a secondary cell group (SCG). A split beareris when a single radio bearer, such as one of the radio bearers providedby the PDCPs 214 and 224 as a service to the SDAPs 215 and 225, ishandled by cell groups in dual connectivity. The PDCPs 214 and 224 maymap/de-map the split radio bearer between RLC channels belonging to cellgroups.

The RLCs 213 and 223 may perform segmentation, retransmission throughAutomatic Repeat Request (ARQ), and removal of duplicate data unitsreceived from MACs 212 and 222, respectively. The RLCs 213 and 223 maysupport three transmission modes: transparent mode (TM); unacknowledgedmode (UM); and acknowledged mode (AM). Based on the transmission mode anRLC is operating, the RLC may perform one or more of the notedfunctions. The RLC configuration may be per logical channel with nodependency on numerologies and/or Transmission Time Interval (TTI)durations. As shown in FIG. 3 , the RLCs 213 and 223 may provide RLCchannels as a service to PDCPs 214 and 224, respectively.

The MACs 212 and 222 may perform multiplexing/demultiplexing of logicalchannels and/or mapping between logical channels and transport channels.The multiplexing/demultiplexing may include multiplexing/demultiplexingof data units, belonging to the one or more logical channels, into/fromTransport Blocks (TBs) delivered to/from the PHYs 211 and 221. The MAC222 may be configured to perform scheduling, scheduling informationreporting, and priority handling between UEs by means of dynamicscheduling. Scheduling may be performed in the gNB 220 (at the MAC 222)for downlink and uplink. The MACs 212 and 222 may be configured toperform error correction through Hybrid Automatic Repeat Request (HARQ)(e.g., one HARQ entity per carrier in case of Carrier Aggregation (CA)),priority handling between logical channels of the UE 210 by means oflogical channel prioritization, and/or padding. The MACs 212 and 222 maysupport one or more numerologies and/or transmission timings. In anexample, mapping restrictions in a logical channel prioritization maycontrol which numerology and/or transmission timing a logical channelmay use. As shown in FIG. 3 , the MACs 212 and 222 may provide logicalchannels as a service to the RLCs 213 and 223.

The PHYs 211 and 221 may perform mapping of transport channels tophysical channels and digital and analog signal processing functions forsending and receiving information over the air interface. These digitaland analog signal processing functions may include, for example,coding/decoding and modulation/demodulation. The PHYs 211 and 221 mayperform multi-antenna mapping. As shown in FIG. 3 , the PHYs 211 and 221may provide one or more transport channels as a service to the MACs 212and 222.

FIG. 4A illustrates an example downlink data flow through the NR userplane protocol stack. FIG. 4A illustrates a downlink data flow of threeIP packets (n, n+1, and m) through the NR user plane protocol stack togenerate two TBs at the gNB 220. An uplink data flow through the NR userplane protocol stack may be similar to the downlink data flow depictedin FIG. 4A.

The downlink data flow of FIG. 4A begins when SDAP 225 receives thethree IP packets from one or more QoS flows and maps the three packetsto radio bearers. In FIG. 4A, the SDAP 225 maps IP packets n and n+1 toa first radio bearer 402 and maps IP packet m to a second radio bearer404. An SDAP header (labeled with an “H” in FIG. 4A) is added to an IPpacket. The data unit from/to a higher protocol layer is referred to asa service data unit (SDU) of the lower protocol layer and the data unitto/from a lower protocol layer is referred to as a protocol data unit(PDU) of the higher protocol layer. As shown in FIG. 4A, the data unitfrom the SDAP 225 is an SDU of lower protocol layer PDCP 224 and is aPDU of the SDAP 225.

The remaining protocol layers in FIG. 4A may perform their associatedfunctionality (e.g., with respect to FIG. 3 ), add correspondingheaders, and forward their respective outputs to the next lower layer.For example, the PDCP 224 may perform IP-header compression andciphering and forward its output to the RLC 223. The RLC 223 mayoptionally perform segmentation (e.g., as shown for IP packet m in FIG.4A) and forward its output to the MAC 222. The MAC 222 may multiplex anumber of RLC PDUs and may attach a MAC subheader to an RLC PDU to forma transport block. In NR, the MAC subheaders may be distributed acrossthe MAC PDU, as illustrated in FIG. 4A. In LTE, the MAC subheaders maybe entirely located at the beginning of the MAC PDU. The NR MAC PDUstructure may reduce processing time and associated latency because theMAC PDU subheaders may be computed before the full MAC PDU is assembled.

FIG. 4B illustrates an example format of a MAC subheader in a MAC PDU.The MAC subheader includes: an SDU length field for indicating thelength (e.g., in bytes) of the MAC SDU to which the MAC subheadercorresponds; a logical channel identifier (LCID) field for identifyingthe logical channel from which the MAC SDU originated to aid in thedemultiplexing process; a flag (F) for indicating the size of the SDUlength field; and a reserved bit (R) field for future use.

FIG. 4B further illustrates MAC control elements (CEs) inserted into theMAC PDU by a MAC, such as MAC 223 or MAC 222. For example, FIG. 4Billustrates two MAC CEs inserted into the MAC PDU. MAC CEs may beinserted at the beginning of a MAC PDU for downlink transmissions (asshown in FIG. 4B) and at the end of a MAC PDU for uplink transmissions.MAC CEs may be used for in-band control signaling. Example MAC CEsinclude: scheduling-related MAC CEs, such as buffer status reports andpower headroom reports; activation/deactivation MAC CEs, such as thosefor activation/deactivation of PDCP duplication detection, channel stateinformation (CSI) reporting, sounding reference signal (SRS)transmission, and prior configured components; discontinuous reception(DRX) related MAC CEs; timing advance MAC CEs; and random access relatedMAC CEs. A MAC CE may be preceded by a MAC subheader with a similarformat as described for MAC SDUs and may be identified with a reservedvalue in the LCID field that indicates the type of control informationincluded in the MAC CE.

Before describing the NR control plane protocol stack, logical channels,transport channels, and physical channels are first described as well asa mapping between the channel types. One or more of the channels may beused to carry out functions associated with the NR control planeprotocol stack described later below.

FIG. 5A and FIG. 5B illustrate, for downlink and uplink respectively, amapping between logical channels, transport channels, and physicalchannels. Information is passed through channels between the RLC, theMAC, and the PHY of the NR protocol stack. A logical channel may be usedbetween the RLC and the MAC and may be classified as a control channelthat carries control and configuration information in the NR controlplane or as a traffic channel that carries data in the NR user plane. Alogical channel may be classified as a dedicated logical channel that isdedicated to a specific UE or as a common logical channel that may beused by more than one UE. A logical channel may also be defined by thetype of information it carries. The set of logical channels defined byNR include, for example:

-   -   a paging control channel (PCCH) for carrying paging messages        used to page a UE whose location is not known to the network on        a cell level;    -   a broadcast control channel (BCCH) for carrying system        information messages in the form of a master information block        (MIB) and several system information blocks (SIBs), wherein the        system information messages may be used by the UEs to obtain        information about how a cell is configured and how to operate        within the cell; a common control channel (CCCH) for carrying        control messages together with random access;    -   a dedicated control channel (DCCH) for carrying control messages        to/from a specific the UE to configure the UE; and    -   a dedicated traffic channel (DTCH) for carrying user data        to/from a specific the UE.

Transport channels are used between the MAC and PHY layers and may bedefined by how the information they carry is transmitted over the airinterface. The set of transport channels defined by NR include, forexample:

-   -   a paging channel (PCH) for carrying paging messages that        originated from the PCCH;    -   a broadcast channel (BCH) for carrying the MIB from the BCCH;    -   a downlink shared channel (DL-SCH) for carrying downlink data        and signaling messages, including the SIBs from the BCCH;    -   an uplink shared channel (UL-SCH) for carrying uplink data and        signaling messages; and    -   a random access channel (RACH) for allowing a UE to contact the        network without any prior scheduling.

The PHY may use physical channels to pass information between processinglevels of the PHY. A physical channel may have an associated set oftime-frequency resources for carrying the information of one or moretransport channels. The PHY may generate control information to supportthe low-level operation of the PHY and provide the control informationto the lower levels of the PHY via physical control channels, known asL1/L2 control channels. The set of physical channels and physicalcontrol channels defined by NR include, for example:

-   -   a physical broadcast channel (PBCH) for carrying the MIB from        the BCH;    -   a physical downlink shared channel (PDSCH) for carrying downlink        data and signaling messages from the DL-SCH, as well as paging        messages from the PCH;    -   a physical downlink control channel (PDCCH) for carrying        downlink control information (DCI), which may include downlink        scheduling commands, uplink scheduling grants, and uplink power        control commands;    -   a physical uplink shared channel (PUSCH) for carrying uplink        data and signaling messages from the UL-SCH and in some        instances uplink control information (UCI) as described below;    -   a physical uplink control channel (PUCCH) for carrying UCI,        which may include HARQ acknowledgments, channel quality        indicators (CQI), pre-coding matrix indicators (PMI), rank        indicators (RI), and scheduling requests (SR); and    -   a physical random access channel (PRACH) for random access.

Similar to the physical control channels, the physical layer generatesphysical signals to support the low-level operation of the physicallayer. As shown in FIG. 5A and FIG. 5B, the physical layer signalsdefined by NR include: primary synchronization signals (PSS), secondarysynchronization signals (SSS), channel state information referencesignals (CSI-RS), demodulation reference signals (DMRS), soundingreference signals (SRS), and phase-tracking reference signals (PT-RS).These physical layer signals will be described in greater detail below.

FIG. 2B illustrates an example NR control plane protocol stack. As shownin FIG. 2B, the NR control plane protocol stack may use the same/similarfirst four protocol layers as the example NR user plane protocol stack.These four protocol layers include the PHYs 211 and 221, the MACs 212and 222, the RLCs 213 and 223, and the PDCPs 214 and 224. Instead ofhaving the SDAPs 215 and 225 at the top of the stack as in the NR userplane protocol stack, the NR control plane stack has radio resourcecontrols (RRCs) 216 and 226 and NAS protocols 217 and 237 at the top ofthe NR control plane protocol stack.

The NAS protocols 217 and 237 may provide control plane functionalitybetween the UE 210 and the AMF 230 (e.g., the AMF 158A) or, moregenerally, between the UE 210 and the CN. The NAS protocols 217 and 237may provide control plane functionality between the UE 210 and the AMF230 via signaling messages, referred to as NAS messages. There is nodirect path between the UE 210 and the AMF 230 through which the NASmessages can be transported. The NAS messages may be transported usingthe AS of the Uu and NG interfaces. NAS protocols 217 and 237 mayprovide control plane functionality such as authentication, security,connection setup, mobility management, and session management.

The RRCs 216 and 226 may provide control plane functionality between theUE 210 and the gNB 220 or, more generally, between the UE 210 and theRAN. The RRCs 216 and 226 may provide control plane functionalitybetween the UE 210 and the gNB 220 via signaling messages, referred toas RRC messages. RRC messages may be transmitted between the UE 210 andthe RAN using signaling radio bearers and the same/similar PDCP, RLC,MAC, and PHY protocol layers. The MAC may multiplex control-plane anduser-plane data into the same transport block (TB). The RRCs 216 and 226may provide control plane functionality such as: broadcast of systeminformation related to AS and NAS; paging initiated by the CN or theRAN; establishment, maintenance and release of an RRC connection betweenthe UE 210 and the RAN; security functions including key management;establishment, configuration, maintenance and release of signaling radiobearers and data radio bearers; mobility functions; QoS managementfunctions; the UE measurement reporting and control of the reporting;detection of and recovery from radio link failure (RLF); and/or NASmessage transfer. As part of establishing an RRC connection, RRCs 216and 226 may establish an RRC context, which may involve configuringparameters for communication between the UE 210 and the RAN.

FIG. 6 is an example diagram showing RRC state transitions of a UE. TheUE may be the same or similar to the wireless device 106 depicted inFIG. 1A, the UE 210 depicted in FIG. 2A and FIG. 2B, or any otherwireless device described in the present disclosure. As illustrated inFIG. 6 , a UE may be in at least one of three RRC states: RRC connected602 (e.g., RRC_CONNECTED), RRC idle 604 (e.g., RRC_IDLE), and RRCinactive 606 (e.g., RRC_INACTIVE).

In RRC connected 602, the UE has an established RRC context and may haveat least one RRC connection with a base station. The base station may besimilar to one of the one or more base stations included in the RAN 104depicted in FIG. 1A, one of the gNBs 160 or ng-eNBs 162 depicted in FIG.1B, the gNB 220 depicted in FIG. 2A and FIG. 2B, or any other basestation described in the present disclosure. The base station with whichthe UE is connected may have the RRC context for the UE. The RRCcontext, referred to as the UE context, may comprise parameters forcommunication between the UE and the base station. These parameters mayinclude, for example: one or more AS contexts; one or more radio linkconfiguration parameters; bearer configuration information (e.g.,relating to a data radio bearer, signaling radio bearer, logicalchannel, QoS flow, and/or PDU session); security information; and/orPHY, MAC, RLC, PDCP, and/or SDAP layer configuration information. Whilein RRC connected 602, mobility of the UE may be managed by the RAN(e.g., the RAN 104 or the NG-RAN 154). The UE may measure the signallevels (e.g., reference signal levels) from a serving cell andneighboring cells and report these measurements to the base stationcurrently serving the UE. The UE's serving base station may request ahandover to a cell of one of the neighboring base stations based on thereported measurements. The RRC state may transition from RRC connected602 to RRC idle 604 through a connection release procedure 608 or to RRCinactive 606 through a connection inactivation procedure 610.

In RRC idle 604, an RRC context may not be established for the UE. InRRC idle 604, the UE may not have an RRC connection with the basestation. While in RRC idle 604, the UE may be in a sleep state for themajority of the time (e.g., to conserve battery power). The UE may wakeup periodically (e.g., once in every discontinuous reception cycle) tomonitor for paging messages from the RAN. Mobility of the UE may bemanaged by the UE through a procedure known as cell reselection. The RRCstate may transition from RRC idle 604 to RRC connected 602 through aconnection establishment procedure 612, which may involve a randomaccess procedure as discussed in greater detail below.

In RRC inactive 606, the RRC context previously established ismaintained in the UE and the base station. This allows for a fasttransition to RRC connected 602 with reduced signaling overhead ascompared to the transition from RRC idle 604 to RRC connected 602. Whilein RRC inactive 606, the UE may be in a sleep state and mobility of theUE may be managed by the UE through cell reselection. The RRC state maytransition from RRC inactive 606 to RRC connected 602 through aconnection resume procedure 614 or to RRC idle 604 though a connectionrelease procedure 616 that may be the same as or similar to connectionrelease procedure 608.

An RRC state may be associated with a mobility management mechanism. InRRC idle 604 and RRC inactive 606, mobility is managed by the UE throughcell reselection. The purpose of mobility management in RRC idle 604 andRRC inactive 606 is to allow the network to be able to notify the UE ofan event via a paging message without having to broadcast the pagingmessage over the entire mobile communications network. The mobilitymanagement mechanism used in RRC idle 604 and RRC inactive 606 may allowthe network to track the UE on a cell-group level so that the pagingmessage may be broadcast over the cells of the cell group that the UEcurrently resides within instead of the entire mobile communicationnetwork. The mobility management mechanisms for RRC idle 604 and RRCinactive 606 track the UE on a cell-group level. They may do so usingdifferent granularities of grouping. For example, there may be threelevels of cell-grouping granularity: individual cells; cells within aRAN area identified by a RAN area identifier (RAI); and cells within agroup of RAN areas, referred to as a tracking area and identified by atracking area identifier (TAI).

Tracking areas may be used to track the UE at the CN level. The CN(e.g., the CN 102 or the 5G-CN 152) may provide the UE with a list ofTAIs associated with a UE registration area. If the UE moves, throughcell reselection, to a cell associated with a TAI not included in thelist of TAIs associated with the UE registration area, the UE mayperform a registration update with the CN to allow the CN to update theUE's location and provide the UE with a new the UE registration area.

RAN areas may be used to track the UE at the RAN level. For a UE in RRCinactive 606 state, the UE may be assigned a RAN notification area. ARAN notification area may comprise one or more cell identities, a listof RAIs, or a list of TAIs. In an example, a base station may belong toone or more RAN notification areas. In an example, a cell may belong toone or more RAN notification areas. If the UE moves, through cellreselection, to a cell not included in the RAN notification areaassigned to the UE, the UE may perform a notification area update withthe RAN to update the UE's RAN notification area.

A base station storing an RRC context for a UE or a last serving basestation of the UE may be referred to as an anchor base station. Ananchor base station may maintain an RRC context for the UE at leastduring a period of time that the UE stays in a RAN notification area ofthe anchor base station and/or during a period of time that the UE staysin RRC inactive 606.

A gNB, such as gNBs 160 in FIG. 1B, may be split in two parts: a centralunit (gNB-CU), and one or more distributed units (gNB-DU). A gNB-CU maybe coupled to one or more gNB-DUs using an F1 interface. The gNB-CU maycomprise the RRC, the PDCP, and the SDAP. A gNB-DU may comprise the RLC,the MAC, and the PHY.

In NR, the physical signals and physical channels (discussed withrespect to FIG. 5A and FIG. 5B) may be mapped onto orthogonal frequencydivisional multiplexing (OFDM) symbols. OFDM is a multicarriercommunication scheme that transmits data over F orthogonal subcarriers(or tones). Before transmission, the data may be mapped to a series ofcomplex symbols (e.g., M-quadrature amplitude modulation (M-QAM) orM-phase shift keying (M-PSK) symbols), referred to as source symbols,and divided into F parallel symbol streams. The F parallel symbolstreams may be treated as though they are in the frequency domain andused as inputs to an Inverse Fast Fourier Transform (IFFT) block thattransforms them into the time domain. The IFFT block may take in Fsource symbols at a time, one from each of the F parallel symbolstreams, and use each source symbol to modulate the amplitude and phaseof one of F sinusoidal basis functions that correspond to the Forthogonal subcarriers. The output of the IFFT block may be Ftime-domain samples that represent the summation of the F orthogonalsubcarriers. The F time-domain samples may form a single OFDM symbol.After some processing (e.g., addition of a cyclic prefix) andup-conversion, an OFDM symbol provided by the IFFT block may betransmitted over the air interface on a carrier frequency. The Fparallel symbol streams may be mixed using an FFT block before beingprocessed by the IFFT block. This operation produces Discrete FourierTransform (DFT)-precoded OFDM symbols and may be used by UEs in theuplink to reduce the peak to average power ratio (PAPR). Inverseprocessing may be performed on the OFDM symbol at a receiver using anFFT block to recover the data mapped to the source symbols.

FIG. 7 illustrates an example configuration of an NR frame into whichOFDM symbols are grouped. An NR frame may be identified by a systemframe number (SFN). The SFN may repeat with a period of 1024 frames. Asillustrated, one NR frame may be 10 milliseconds (ms) in duration andmay include 10 subframes that are 1 ms in duration. A subframe may bedivided into slots that include, for example, 14 OFDM symbols per slot.

The duration of a slot may depend on the numerology used for the OFDMsymbols of the slot. In NR, a flexible numerology is supported toaccommodate different cell deployments (e.g., cells with carrierfrequencies below 1 GHz up to cells with carrier frequencies in themm-wave range). A numerology may be defined in terms of subcarrierspacing and cyclic prefix duration. For a numerology in NR, subcarrierspacings may be scaled up by powers of two from a baseline subcarrierspacing of 15 kHz, and cyclic prefix durations may be scaled down bypowers of two from a baseline cyclic prefix duration of 4.7 μs. Forexample, NR defines numerologies with the following subcarrierspacing/cyclic prefix duration combinations: 15 kHz/4.7 μs; 30 kHz/2.3μs; 60 kHz/1.2 μs; 120 kHz/0.59 μs; and 240 kHz/0.29 μs.

A slot may have a fixed number of OFDM symbols (e.g., 14 OFDM symbols).A numerology with a higher subcarrier spacing has a shorter slotduration and, correspondingly, more slots per subframe. FIG. 7illustrates this numerology-dependent slot duration andslots-per-subframe transmission structure (the numerology with asubcarrier spacing of 240 kHz is not shown in FIG. 7 for ease ofillustration). A subframe in NR may be used as a numerology-independenttime reference, while a slot may be used as the unit upon which uplinkand downlink transmissions are scheduled. To support low latency,scheduling in NR may be decoupled from the slot duration and start atany OFDM symbol and last for as many symbols as needed for atransmission. These partial slot transmissions may be referred to asmini-slot or subslot transmissions.

FIG. 8 illustrates an example configuration of a slot in the time andfrequency domain for an NR carrier. The slot includes resource elements(REs) and resource blocks (RBs). An RE is the smallest physical resourcein NR. An RE spans one OFDM symbol in the time domain by one subcarrierin the frequency domain as shown in FIG. 8 . An RB spans twelveconsecutive REs in the frequency domain as shown in FIG. 8 . An NRcarrier may be limited to a width of 275 RBs or 275×12=3300 subcarriers.Such a limitation, if used, may limit the NR carrier to 50, 100, 200,and 400 MHz for subcarrier spacings of 15, 30, 60, and 120 kHz,respectively, where the 400 MHz bandwidth may be set based on a 400 MHzper carrier bandwidth limit.

FIG. 8 illustrates a single numerology being used across the entirebandwidth of the NR carrier. In other example configurations, multiplenumerologies may be supported on the same carrier.

NR may support wide carrier bandwidths (e.g., up to 400 MHz for asubcarrier spacing of 120 kHz). Not all UEs may be able to receive thefull carrier bandwidth (e.g., due to hardware limitations). Also,receiving the full carrier bandwidth may be prohibitive in terms of UEpower consumption. In an example, to reduce power consumption and/or forother purposes, a UE may adapt the size of the UE's receive bandwidthbased on the amount of traffic the UE is scheduled to receive. This isreferred to as bandwidth adaptation.

NR defines bandwidth parts (BWPs) to support UEs not capable ofreceiving the full carrier bandwidth and to support bandwidthadaptation. In an example, a BWP may be defined by a subset ofcontiguous RBs on a carrier. A UE may be configured (e.g., via RRClayer) with one or more downlink BWPs and one or more uplink BWPs perserving cell (e.g., up to four downlink BWPs and up to four uplink BWPsper serving cell). At a given time, one or more of the configured BWPsfor a serving cell may be active. These one or more BWPs may be referredto as active BWPs of the serving cell. When a serving cell is configuredwith a secondary uplink carrier, the serving cell may have one or morefirst active BWPs in the uplink carrier and one or more second activeBWPs in the secondary uplink carrier.

For unpaired spectra, a downlink BWP from a set of configured downlinkBWPs may be linked with an uplink BWP from a set of configured uplinkBWPs if a downlink BWP index of the downlink BWP and an uplink BWP indexof the uplink BWP are the same. For unpaired spectra, a UE may expectthat a center frequency for a downlink BWP is the same as a centerfrequency for an uplink BWP.

For a downlink BWP in a set of configured downlink BWPs on a primarycell (PCell), a base station may configure a UE with one or more controlresource sets (CORESETs) for at least one search space. A search spaceis a set of locations in the time and frequency domains where the UE mayfind control information. The search space may be a UE-specific searchspace or a common search space (potentially usable by a plurality ofUEs). For example, a base station may configure a UE with a commonsearch space, on a PCell or on a primary secondary cell (PSCell), in anactive downlink BWP.

For an uplink BWP in a set of configured uplink BWPs, a BS may configurea UE with one or more resource sets for one or more PUCCH transmissions.A UE may receive downlink receptions (e.g., PDCCH or PDSCH) in adownlink BWP according to a configured numerology (e.g., subcarrierspacing and cyclic prefix duration) for the downlink BWP. The UE maytransmit uplink transmissions (e.g., PUCCH or PUSCH) in an uplink BWPaccording to a configured numerology (e.g., subcarrier spacing andcyclic prefix length for the uplink BWP).

One or more BWP indicator fields may be provided in Downlink ControlInformation (DCI). A value of a BWP indicator field may indicate whichBWP in a set of configured BWPs is an active downlink BWP for one ormore downlink receptions. The value of the one or more BWP indicatorfields may indicate an active uplink BWP for one or more uplinktransmissions.

A base station may semi-statically configure a UE with a defaultdownlink BWP within a set of configured downlink BWPs associated with aPCell. If the base station does not provide the default downlink BWP tothe UE, the default downlink BWP may be an initial active downlink BWP.The UE may determine which BWP is the initial active downlink BWP basedon a CORESET configuration obtained using the PBCH.

A base station may configure a UE with a BWP inactivity timer value fora PCell. The UE may start or restart a BWP inactivity timer at anyappropriate time. For example, the UE may start or restart the BWPinactivity timer (a) when the UE detects a DCI indicating an activedownlink BWP other than a default downlink BWP for a paired spectraoperation; or (b) when a UE detects a DCI indicating an active downlinkBWP or active uplink BWP other than a default downlink BWP or uplink BWPfor an unpaired spectra operation. If the UE does not detect DCI duringan interval of time (e.g., 1 ms or 0.5 ms), the UE may run the BWPinactivity timer toward expiration (for example, increment from zero tothe BWP inactivity timer value, or decrement from the BWP inactivitytimer value to zero). When the BWP inactivity timer expires, the UE mayswitch from the active downlink BWP to the default downlink BWP.

In an example, a base station may semi-statically configure a UE withone or more BWPs. A UE may switch an active BWP from a first BWP to asecond BWP in response to receiving a DCI indicating the second BWP asan active BWP and/or in response to an expiry of the BWP inactivitytimer (e.g., if the second BWP is the default BWP).

Downlink and uplink BWP switching (where BWP switching refers toswitching from a currently active BWP to a not currently active BWP) maybe performed independently in paired spectra. In unpaired spectra,downlink and uplink BWP switching may be performed simultaneously.Switching between configured BWPs may occur based on RRC signaling, DCI,expiration of a BWP inactivity timer, and/or an initiation of randomaccess.

FIG. 9 illustrates an example of bandwidth adaptation using threeconfigured BWPs for an NR carrier. A UE configured with the three BWPsmay switch from one BWP to another BWP at a switching point. In theexample illustrated in FIG. 9 , the BWPs include: a BWP 902 with abandwidth of 40 MHz and a subcarrier spacing of 15 kHz; a BWP 904 with abandwidth of 10 MHz and a subcarrier spacing of 15 kHz; and a BWP 906with a bandwidth of 20 MHz and a subcarrier spacing of 60 kHz. The BWP902 may be an initial active BWP, and the BWP 904 may be a default BWP.The UE may switch between BWPs at switching points. In the example ofFIG. 9 , the UE may switch from the BWP 902 to the BWP 904 at aswitching point 908. The switching at the switching point 908 may occurfor any suitable reason, for example, in response to an expiry of a BWPinactivity timer (indicating switching to the default BWP) and/or inresponse to receiving a DCI indicating BWP 904 as the active BWP. The UEmay switch at a switching point 910 from active BWP 904 to BWP 906 inresponse receiving a DCI indicating BWP 906 as the active BWP. The UEmay switch at a switching point 912 from active BWP 906 to BWP 904 inresponse to an expiry of a BWP inactivity timer and/or in responsereceiving a DCI indicating BWP 904 as the active BWP. The UE may switchat a switching point 914 from active BWP 904 to BWP 902 in responsereceiving a DCI indicating BWP 902 as the active BWP.

If a UE is configured for a secondary cell with a default downlink BWPin a set of configured downlink BWPs and a timer value, UE proceduresfor switching BWPs on a secondary cell may be the same/similar as thoseon a primary cell. For example, the UE may use the timer value and thedefault downlink BWP for the secondary cell in the same/similar manneras the UE would use these values for a primary cell.

To provide for greater data rates, two or more carriers can beaggregated and simultaneously transmitted to/from the same UE usingcarrier aggregation (CA). The aggregated carriers in CA may be referredto as component carriers (CCs). When CA is used, there are a number ofserving cells for the UE, one for a CC. The CCs may have threeconfigurations in the frequency domain.

FIG. 10A illustrates the three CA configurations with two CCs. In theintraband, contiguous configuration 1002, the two CCs are aggregated inthe same frequency band (frequency band A) and are located directlyadjacent to each other within the frequency band. In the intraband,non-contiguous configuration 1004, the two CCs are aggregated in thesame frequency band (frequency band A) and are separated in thefrequency band by a gap. In the interband configuration 1006, the twoCCs are located in frequency bands (frequency band A and frequency bandB).

In an example, up to 32 CCs may be aggregated. The aggregated CCs mayhave the same or different bandwidths, subcarrier spacing, and/orduplexing schemes (TDD or FDD). A serving cell for a UE using CA mayhave a downlink CC. For FDD, one or more uplink CCs may be optionallyconfigured for a serving cell. The ability to aggregate more downlinkcarriers than uplink carriers may be useful, for example, when the UEhas more data traffic in the downlink than in the uplink.

When CA is used, one of the aggregated cells for a UE may be referred toas a primary cell (PCell). The PCell may be the serving cell that the UEinitially connects to at RRC connection establishment, reestablishment,and/or handover. The PCell may provide the UE with NAS mobilityinformation and the security input. UEs may have different PCells. Inthe downlink, the carrier corresponding to the PCell may be referred toas the downlink primary CC (DL PCC). In the uplink, the carriercorresponding to the PCell may be referred to as the uplink primary CC(UL PCC). The other aggregated cells for the UE may be referred to assecondary cells (SCells). In an example, the SCells may be configuredafter the PCell is configured for the UE. For example, an SCell may beconfigured through an RRC Connection Reconfiguration procedure. In thedownlink, the carrier corresponding to an SCell may be referred to as adownlink secondary CC (DL SCC). In the uplink, the carrier correspondingto the SCell may be referred to as the uplink secondary CC (UL SCC).

Configured SCells for a UE may be activated and deactivated based on,for example, traffic and channel conditions. Deactivation of an SCellmay mean that PDCCH and PDSCH reception on the SCell is stopped andPUSCH, SRS, and CQI transmissions on the SCell are stopped. ConfiguredSCells may be activated and deactivated using a MAC CE with respect toFIG. 4B. For example, a MAC CE may use a bitmap (e.g., one bit perSCell) to indicate which SCells (e.g., in a subset of configured SCells)for the UE are activated or deactivated. Configured SCells may bedeactivated in response to an expiration of an SCell deactivation timer(e.g., one SCell deactivation timer per SCell).

Downlink control information, such as scheduling assignments andscheduling grants, for a cell may be transmitted on the cellcorresponding to the assignments and grants, which is known asself-scheduling. The DCI for the cell may be transmitted on anothercell, which is known as cross-carrier scheduling. Uplink controlinformation (e.g., HARQ acknowledgments and channel state feedback, suchas CQI, PMI, and/or RI) for aggregated cells may be transmitted on thePUCCH of the PCell. For a larger number of aggregated downlink CCs, thePUCCH of the PCell may become overloaded. Cells may be divided intomultiple PUCCH groups.

FIG. 10B illustrates an example of how aggregated cells may beconfigured into one or more PUCCH groups. A PUCCH group 1010 and a PUCCHgroup 1050 may include one or more downlink CCs, respectively. In theexample of FIG. 10B, the PUCCH group 1010 includes three downlink CCs: aPCell 1011, an SCell 1012, and an SCell 1013. The PUCCH group 1050includes three downlink CCs in the present example: a PCell 1051, anSCell 1052, and an SCell 1053. One or more uplink CCs may be configuredas a PCell 1021, an SCell 1022, and an SCell 1023. One or more otheruplink CCs may be configured as a primary Scell (PSCell) 1061, an SCell1062, and an SCell 1063. Uplink control information (UCI) related to thedownlink CCs of the PUCCH group 1010, shown as UCI 1031, UCI 1032, andUCI 1033, may be transmitted in the uplink of the PCell 1021. Uplinkcontrol information (UCI) related to the downlink CCs of the PUCCH group1050, shown as UCI 1071, UCI 1072, and UCI 1073, may be transmitted inthe uplink of the PSCell 1061. In an example, if the aggregated cellsdepicted in FIG. 10B were not divided into the PUCCH group 1010 and thePUCCH group 1050, a single uplink PCell to transmit UCI relating to thedownlink CCs, and the PCell may become overloaded. By dividingtransmissions of UCI between the PCell 1021 and the PSCell 1061,overloading may be prevented.

A cell, comprising a downlink carrier and optionally an uplink carrier,may be assigned with a physical cell ID and a cell index. The physicalcell ID or the cell index may identify a downlink carrier and/or anuplink carrier of the cell, for example, depending on the context inwhich the physical cell ID is used. A physical cell ID may be determinedusing a synchronization signal transmitted on a downlink componentcarrier. A cell index may be determined using RRC messages. In thedisclosure, a physical cell ID may be referred to as a carrier ID, and acell index may be referred to as a carrier index. For example, when thedisclosure refers to a first physical cell ID for a first downlinkcarrier, the disclosure may mean the first physical cell ID is for acell comprising the first downlink carrier. The same/similar concept mayapply to, for example, a carrier activation. When the disclosureindicates that a first carrier is activated, the specification may meanthat a cell comprising the first carrier is activated.

In CA, a multi-carrier nature of a PHY may be exposed to a MAC. In anexample, a HARQ entity may operate on a serving cell. A transport blockmay be generated per assignment/grant per serving cell. A transportblock and potential HARQ retransmissions of the transport block may bemapped to a serving cell.

In the downlink, a base station may transmit (e.g., unicast, multicast,and/or broadcast) one or more Reference Signals (RSs) to a UE (e.g.,PSS, SSS, CSI-RS, DMRS, and/or PT-RS, as shown in FIG. 5A). In theuplink, the UE may transmit one or more RSs to the base station (e.g.,DMRS, PT-RS, and/or SRS, as shown in FIG. 5B). The PSS and the SSS maybe transmitted by the base station and used by the UE to synchronize theUE to the base station. The PSS and the SSS may be provided in asynchronization signal (SS)/physical broadcast channel (PBCH) block thatincludes the PSS, the SSS, and the PBCH. The base station mayperiodically transmit a burst of SS/PBCH blocks.

FIG. 11A illustrates an example of an SS/PBCH block's structure andlocation. A burst of SS/PBCH blocks may include one or more SS/PBCHblocks (e.g., 4 SS/PBCH blocks, as shown in FIG. 11A). Bursts may betransmitted periodically (e.g., every 2 frames or 20 ms). A burst may berestricted to a half-frame (e.g., a first half-frame having a durationof 5 ms). It will be understood that FIG. 11A is an example, and thatthese parameters (number of SS/PBCH blocks per burst, periodicity ofbursts, position of burst within the frame) may be configured based on,for example: a carrier frequency of a cell in which the SS/PBCH block istransmitted; a numerology or subcarrier spacing of the cell; aconfiguration by the network (e.g., using RRC signaling); or any othersuitable factor. In an example, the UE may assume a subcarrier spacingfor the SS/PBCH block based on the carrier frequency being monitored,unless the radio network configured the UE to assume a differentsubcarrier spacing.

The SS/PBCH block may span one or more OFDM symbols in the time domain(e.g., 4 OFDM symbols, as shown in the example of FIG. 11A) and may spanone or more subcarriers in the frequency domain (e.g., 240 contiguoussubcarriers). The PSS, the SSS, and the PBCH may have a common centerfrequency. The PSS may be transmitted first and may span, for example, 1OFDM symbol and 127 subcarriers. The SSS may be transmitted after thePSS (e.g., two symbols later) and may span 1 OFDM symbol and 127subcarriers. The PBCH may be transmitted after the PSS (e.g., across thenext 3 OFDM symbols) and may span 240 subcarriers.

The location of the SS/PBCH block in the time and frequency domains maynot be known to the UE (e.g., if the UE is searching for the cell). Tofind and select the cell, the UE may monitor a carrier for the PSS. Forexample, the UE may monitor a frequency location within the carrier. Ifthe PSS is not found after a certain duration (e.g., 20 ms), the UE maysearch for the PSS at a different frequency location within the carrier,as indicated by a synchronization raster. If the PSS is found at alocation in the time and frequency domains, the UE may determine, basedon a known structure of the SS/PBCH block, the locations of the SSS andthe PBCH, respectively. The SS/PBCH block may be a cell-defining SSblock (CD-SSB). In an example, a primary cell may be associated with aCD-SSB. The CD-SSB may be located on a synchronization raster. In anexample, a cell selection/search and/or reselection may be based on theCD-SSB.

The SS/PBCH block may be used by the UE to determine one or moreparameters of the cell. For example, the UE may determine a physicalcell identifier (PCI) of the cell based on the sequences of the PSS andthe SSS, respectively. The UE may determine a location of a frameboundary of the cell based on the location of the SS/PBCH block. Forexample, the SS/PBCH block may indicate that it has been transmitted inaccordance with a transmission pattern, wherein a SS/PBCH block in thetransmission pattern is a known distance from the frame boundary.

The PBCH may use a QPSK modulation and may use forward error correction(FEC). The FEC may use polar coding. One or more symbols spanned by thePBCH may carry one or more DMRSs for demodulation of the PBCH. The PBCHmay include an indication of a current system frame number (SFN) of thecell and/or a SS/PBCH block timing index. These parameters mayfacilitate time synchronization of the UE to the base station. The PBCHmay include a master information block (MIB) used to provide the UE withone or more parameters. The MIB may be used by the UE to locateremaining minimum system information (RMSI) associated with the cell.The RMSI may include a System Information Block Type 1 (SIB1). The SIB1may contain information needed by the UE to access the cell. The UE mayuse one or more parameters of the MIB to monitor PDCCH, which may beused to schedule PDSCH. The PDSCH may include the SIB1. The SIB1 may bedecoded using parameters provided in the MIB. The PBCH may indicate anabsence of SIB1. Based on the PBCH indicating the absence of SIB1, theUE may be pointed to a frequency. The UE may search for an SS/PBCH blockat the frequency to which the UE is pointed.

The UE may assume that one or more SS/PBCH blocks transmitted with asame SS/PBCH block index are quasi co-located (QCLed) (e.g., having thesame/similar Doppler spread, Doppler shift, average gain, average delay,and/or spatial Rx parameters). The UE may not assume QCL for SS/PBCHblock transmissions having different SS/PBCH block indices. SS/PBCHblocks (e.g., those within a half-frame) may be transmitted in spatialdirections (e.g., using different beams that span a coverage area of thecell). In an example, a first SS/PBCH block may be transmitted in afirst spatial direction using a first beam, and a second SS/PBCH blockmay be transmitted in a second spatial direction using a second beam.

In an example, within a frequency span of a carrier, a base station maytransmit a plurality of SS/PBCH blocks. In an example, a first PCI of afirst SS/PBCH block of the plurality of SS/PBCH blocks may be differentfrom a second PCI of a second SS/PBCH block of the plurality of SS/PBCHblocks. The PCIs of SS/PBCH blocks transmitted in different frequencylocations may be different or the same.

The CSI-RS may be transmitted by the base station and used by the UE toacquire channel state information (CSI). The base station may configurethe UE with one or more CSI-RSs for channel estimation or any othersuitable purpose. The base station may configure a UE with one or moreof the same/similar CSI-RSs. The UE may measure the one or more CSI-RSs.The UE may estimate a downlink channel state and/or generate a CSIreport based on the measuring of the one or more downlink CSI-RSs. TheUE may provide the CSI report to the base station. The base station mayuse feedback provided by the UE (e.g., the estimated downlink channelstate) to perform link adaptation.

The base station may semi-statically configure the UE with one or moreCSI-RS resource sets. A CSI-RS resource may be associated with alocation in the time and frequency domains and a periodicity. The basestation may selectively activate and/or deactivate a CSI-RS resource.The base station may indicate to the UE that a CSI-RS resource in theCSI-RS resource set is activated and/or deactivated.

The base station may configure the UE to report CSI measurements. Thebase station may configure the UE to provide CSI reports periodically,aperiodically, or semi-persistently. For periodic CSI reporting, the UEmay be configured with a timing and/or periodicity of a plurality of CSIreports. For aperiodic CSI reporting, the base station may request a CSIreport. For example, the base station may command the UE to measure aconfigured CSI-RS resource and provide a CSI report relating to themeasurements. For semi-persistent CSI reporting, the base station mayconfigure the UE to transmit periodically, and selectively activate ordeactivate the periodic reporting. The base station may configure the UEwith a CSI-RS resource set and CSI reports using RRC signaling.

The CSI-RS configuration may comprise one or more parameters indicating,for example, up to 32 antenna ports. The UE may be configured to employthe same OFDM symbols for a downlink CSI-RS and a control resource set(CORESET) when the downlink CSI-RS and CORESET are spatially QCLed andresource elements associated with the downlink CSI-RS are outside of thephysical resource blocks (PRBs) configured for the CORESET. The UE maybe configured to employ the same OFDM symbols for downlink CSI-RS andSS/PBCH blocks when the downlink CSI-RS and SS/PBCH blocks are spatiallyQCLed and resource elements associated with the downlink CSI-RS areoutside of PRBs configured for the SS/PBCH blocks.

Downlink DMRSs may be transmitted by a base station and used by a UE forchannel estimation. For example, the downlink DMRS may be used forcoherent demodulation of one or more downlink physical channels (e.g.,PDSCH). An NR network may support one or more variable and/orconfigurable DMRS patterns for data demodulation. At least one downlinkDMRS configuration may support a front-loaded DMRS pattern. Afront-loaded DMRS may be mapped over one or more OFDM symbols (e.g., oneor two adjacent OFDM symbols). A base station may semi-staticallyconfigure the UE with a number (e.g. a maximum number) of front-loadedDMRS symbols for PDSCH. A DMRS configuration may support one or moreDMRS ports. For example, for single user-MIMO, a DMRS configuration maysupport up to eight orthogonal downlink DMRS ports per UE. Formultiuser-MIMO, a DMRS configuration may support up to 4 orthogonaldownlink DMRS ports per UE. A radio network may support (e.g., at leastfor CP-OFDM) a common DMRS structure for downlink and uplink, wherein aDMRS location, a DMRS pattern, and/or a scrambling sequence may be thesame or different. The base station may transmit a downlink DMRS and acorresponding PDSCH using the same precoding matrix. The UE may use theone or more downlink DMRSs for coherent demodulation/channel estimationof the PDSCH.

In an example, a transmitter (e.g., a base station) may use a precodermatrices for a part of a transmission bandwidth. For example, thetransmitter may use a first precoder matrix for a first bandwidth and asecond precoder matrix for a second bandwidth. The first precoder matrixand the second precoder matrix may be different based on the firstbandwidth being different from the second bandwidth. The UE may assumethat a same precoding matrix is used across a set of PRBs. The set ofPRBs may be denoted as a precoding resource block group (PRG).

A PDSCH may comprise one or more layers. The UE may assume that at leastone symbol with DMRS is present on a layer of the one or more layers ofthe PDSCH. A higher layer may configure up to 3 DMRSs for the PDSCH.

Downlink PT-RS may be transmitted by a base station and used by a UE forphase-noise compensation. Whether a downlink PT-RS is present or not maydepend on an RRC configuration. The presence and/or pattern of thedownlink PT-RS may be configured on a UE-specific basis using acombination of RRC signaling and/or an association with one or moreparameters employed for other purposes (e.g., modulation and codingscheme (MCS)), which may be indicated by DCI. When configured, a dynamicpresence of a downlink PT-RS may be associated with one or more DCIparameters comprising at least MCS. An NR network may support aplurality of PT-RS densities defined in the time and/or frequencydomains. When present, a frequency domain density may be associated withat least one configuration of a scheduled bandwidth. The UE may assume asame precoding for a DMRS port and a PT-RS port. A number of PT-RS portsmay be fewer than a number of DMRS ports in a scheduled resource.Downlink PT-RS may be confined in the scheduled time/frequency durationfor the UE. Downlink PT-RS may be transmitted on symbols to facilitatephase tracking at the receiver.

The UE may transmit an uplink DMRS to a base station for channelestimation. For example, the base station may use the uplink DMRS forcoherent demodulation of one or more uplink physical channels. Forexample, the UE may transmit an uplink DMRS with a PUSCH and/or a PUCCH.The uplink DM-RS may span a range of frequencies that is similar to arange of frequencies associated with the corresponding physical channel.The base station may configure the UE with one or more uplink DMRSconfigurations. At least one DMRS configuration may support afront-loaded DMRS pattern. The front-loaded DMRS may be mapped over oneor more OFDM symbols (e.g., one or two adjacent OFDM symbols). One ormore uplink DMRSs may be configured to transmit at one or more symbolsof a PUSCH and/or a PUCCH. The base station may semi-staticallyconfigure the UE with a number (e.g. maximum number) of front-loadedDMRS symbols for the PUSCH and/or the PUCCH, which the UE may use toschedule a single-symbol DMRS and/or a double-symbol DMRS. An NR networkmay support (e.g., for cyclic prefix orthogonal frequency divisionmultiplexing (CP-OFDM)) a common DMRS structure for downlink and uplink,wherein a DMRS location, a DMRS pattern, and/or a scrambling sequencefor the DMRS may be the same or different.

A PUSCH may comprise one or more layers, and the UE may transmit atleast one symbol with DMRS present on a layer of the one or more layersof the PUSCH. In an example, a higher layer may configure up to threeDMRSs for the PUSCH.

Uplink PT-RS (which may be used by a base station for phase trackingand/or phase-noise compensation) may or may not be present depending onan RRC configuration of the UE. The presence and/or pattern of uplinkPT-RS may be configured on a UE-specific basis by a combination of RRCsignaling and/or one or more parameters employed for other purposes(e.g., Modulation and Coding Scheme (MCS)), which may be indicated byDCI. When configured, a dynamic presence of uplink PT-RS may beassociated with one or more DCI parameters comprising at least MCS. Aradio network may support a plurality of uplink PT-RS densities definedin time/frequency domain. When present, a frequency domain density maybe associated with at least one configuration of a scheduled bandwidth.The UE may assume a same precoding for a DMRS port and a PT-RS port. Anumber of PT-RS ports may be fewer than a number of DMRS ports in ascheduled resource. For example, uplink PT-RS may be confined in thescheduled time/frequency duration for the UE.

SRS may be transmitted by a UE to a base station for channel stateestimation to support uplink channel dependent scheduling and/or linkadaptation. SRS transmitted by the UE may allow a base station toestimate an uplink channel state at one or more frequencies. A schedulerat the base station may employ the estimated uplink channel state toassign one or more resource blocks for an uplink PUSCH transmission fromthe UE. The base station may semi-statically configure the UE with oneor more SRS resource sets. For an SRS resource set, the base station mayconfigure the UE with one or more SRS resources. An SRS resource setapplicability may be configured by a higher layer (e.g., RRC) parameter.For example, when a higher layer parameter indicates beam management, anSRS resource in a SRS resource set of the one or more SRS resource sets(e.g., with the same/similar time domain behavior, periodic, aperiodic,and/or the like) may be transmitted at a time instant (e.g.,simultaneously). The UE may transmit one or more SRS resources in SRSresource sets. An NR network may support aperiodic, periodic and/orsemi-persistent SRS transmissions. The UE may transmit SRS resourcesbased on one or more trigger types, wherein the one or more triggertypes may comprise higher layer signaling (e.g., RRC) and/or one or moreDCI formats. In an example, at least one DCI format may be employed forthe UE to select at least one of one or more configured SRS resourcesets. An SRS trigger type 0 may refer to an SRS triggered based on ahigher layer signaling. An SRS trigger type 1 may refer to an SRStriggered based on one or more DCI formats. In an example, when PUSCHand SRS are transmitted in a same slot, the UE may be configured totransmit SRS after a transmission of a PUSCH and a corresponding uplinkDMRS.

The base station may semi-statically configure the UE with one or moreSRS configuration parameters indicating at least one of following: a SRSresource configuration identifier; a number of SRS ports; time domainbehavior of an SRS resource configuration (e.g., an indication ofperiodic, semi-persistent, or aperiodic SRS); slot, mini-slot, and/orsubframe level periodicity; offset for a periodic and/or an aperiodicSRS resource; a number of OFDM symbols in an SRS resource; a startingOFDM symbol of an SRS resource; an SRS bandwidth; a frequency hoppingbandwidth; a cyclic shift; and/or an SRS sequence ID.

An antenna port is defined such that the channel over which a symbol onthe antenna port is conveyed can be inferred from the channel over whichanother symbol on the same antenna port is conveyed. If a first symboland a second symbol are transmitted on the same antenna port, thereceiver may infer the channel (e.g., fading gain, multipath delay,and/or the like) for conveying the second symbol on the antenna port,from the channel for conveying the first symbol on the antenna port. Afirst antenna port and a second antenna port may be referred to as quasico-located (QCLed) if one or more large-scale properties of the channelover which a first symbol on the first antenna port is conveyed may beinferred from the channel over which a second symbol on a second antennaport is conveyed. The one or more large-scale properties may comprise atleast one of: a delay spread; a Doppler spread; a Doppler shift; anaverage gain; an average delay; and/or spatial Receiving (Rx)parameters.

Channels that use beamforming require beam management. Beam managementmay comprise beam measurement, beam selection, and beam indication. Abeam may be associated with one or more reference signals. For example,a beam may be identified by one or more beamformed reference signals.The UE may perform downlink beam measurement based on downlink referencesignals (e.g., a channel state information reference signal (CSI-RS))and generate a beam measurement report. The UE may perform the downlinkbeam measurement procedure after an RRC connection is set up with a basestation.

FIG. 11B illustrates an example of channel state information referencesignals (CSI-RSs) that are mapped in the time and frequency domains. Asquare shown in FIG. 11B may span a resource block (RB) within abandwidth of a cell. A base station may transmit one or more RRCmessages comprising CSI-RS resource configuration parameters indicatingone or more CSI-RSs. One or more of the following parameters may beconfigured by higher layer signaling (e.g., RRC and/or MAC signaling)for a CSI-RS resource configuration: a CSI-RS resource configurationidentity, a number of CSI-RS ports, a CSI-RS configuration (e.g., symboland resource element (RE) locations in a subframe), a CSI-RS subframeconfiguration (e.g., subframe location, offset, and periodicity in aradio frame), a CSI-RS power parameter, a CSI-RS sequence parameter, acode division multiplexing (CDM) type parameter, a frequency density, atransmission comb, quasi co-location (QCL) parameters (e.g.,QCL-scramblingidentity, crs-portscount, mbsfn-subframeconfiglist,csi-rs-configZPid, qcl-csi-rs-configNZPid), and/or other radio resourceparameters.

The three beams illustrated in FIG. 11B may be configured for a UE in aUE-specific configuration. Three beams are illustrated in FIG. 11B (beam#1, beam #2, and beam #3), more or fewer beams may be configured. Beam#1 may be allocated with CSI-RS 1101 that may be transmitted in one ormore subcarriers in an RB of a first symbol. Beam #2 may be allocatedwith CSI-RS 1102 that may be transmitted in one or more subcarriers inan RB of a second symbol. Beam #3 may be allocated with CSI-RS 1103 thatmay be transmitted in one or more subcarriers in an RB of a thirdsymbol. By using frequency division multiplexing (FDM), a base stationmay use other subcarriers in a same RB (for example, those that are notused to transmit CSI-RS 1101) to transmit another CSI-RS associated witha beam for another UE. By using time domain multiplexing (TDM), beamsused for the UE may be configured such that beams for the UE use symbolsfrom beams of other UEs.

CSI-RSs such as those illustrated in FIG. 11B (e.g., CSI-RS 1101, 1102,1103) may be transmitted by the base station and used by the UE for oneor more measurements. For example, the UE may measure a reference signalreceived power (RSRP) of configured CSI-RS resources. The base stationmay configure the UE with a reporting configuration and the UE mayreport the RSRP measurements to a network (for example, via one or morebase stations) based on the reporting configuration. In an example, thebase station may determine, based on the reported measurement results,one or more transmission configuration indication (TCI) statescomprising a number of reference signals. In an example, the basestation may indicate one or more TCI states to the UE (e.g., via RRCsignaling, a MAC CE, and/or a DCI). The UE may receive a downlinktransmission with a receive (Rx) beam determined based on the one ormore TCI states. In an example, the UE may or may not have a capabilityof beam correspondence. If the UE has the capability of beamcorrespondence, the UE may determine a spatial domain filter of atransmit (Tx) beam based on a spatial domain filter of the correspondingRx beam. If the UE does not have the capability of beam correspondence,the UE may perform an uplink beam selection procedure to determine thespatial domain filter of the Tx beam. The UE may perform the uplink beamselection procedure based on one or more sounding reference signal (SRS)resources configured to the UE by the base station. The base station mayselect and indicate uplink beams for the UE based on measurements of theone or more SRS resources transmitted by the UE.

In a beam management procedure, a UE may assess (e.g., measure) achannel quality of one or more beam pair links, a beam pair linkcomprising a transmitting beam transmitted by a base station and areceiving beam received by the UE. Based on the assessment, the UE maytransmit a beam measurement report indicating one or more beam pairquality parameters comprising, e.g., one or more beam identifications(e.g., a beam index, a reference signal index, or the like), RSRP, aprecoding matrix indicator (PMI), a channel quality indicator (CQI),and/or a rank indicator (RI).

FIG. 12A illustrates examples of three downlink beam managementprocedures: P1, P2, and P3. Procedure P1 may enable a UE measurement ontransmit (Tx) beams of a transmission reception point (TRP) (or multipleTRPs), e.g., to support a selection of one or more base station Tx beamsand/or UE Rx beams (shown as ovals in the top row and bottom row,respectively, of P1). Beamforming at a TRP may comprise a Tx beam sweepfor a set of beams (shown, in the top rows of P1 and P2, as ovalsrotated in a counter-clockwise direction indicated by the dashed arrow).Beamforming at a UE may comprise an Rx beam sweep for a set of beams(shown, in the bottom rows of P1 and P3, as ovals rotated in a clockwisedirection indicated by the dashed arrow). Procedure P2 may be used toenable a UE measurement on Tx beams of a TRP (shown, in the top row ofP2, as ovals rotated in a counter-clockwise direction indicated by thedashed arrow). The UE and/or the base station may perform procedure P2using a smaller set of beams than is used in procedure P1, or usingnarrower beams than the beams used in procedure P1. This may be referredto as beam refinement. The UE may perform procedure P3 for Rx beamdetermination by using the same Tx beam at the base station and sweepingan Rx beam at the UE.

FIG. 12B illustrates examples of three uplink beam managementprocedures: U1, U2, and U3. Procedure U1 may be used to enable a basestation to perform a measurement on Tx beams of a UE, e.g., to support aselection of one or more UE Tx beams and/or base station Rx beams (shownas ovals in the top row and bottom row, respectively, of U1).Beamforming at the UE may include, e.g., a Tx beam sweep from a set ofbeams (shown in the bottom rows of U1 and U3 as ovals rotated in aclockwise direction indicated by the dashed arrow). Beamforming at thebase station may include, e.g., an Rx beam sweep from a set of beams(shown, in the top rows of U1 and U2, as ovals rotated in acounter-clockwise direction indicated by the dashed arrow). Procedure U2may be used to enable the base station to adjust its Rx beam when the UEuses a fixed Tx beam. The UE and/or the base station may performprocedure U2 using a smaller set of beams than is used in procedure P1,or using narrower beams than the beams used in procedure P1. This may bereferred to as beam refinement The UE may perform procedure U3 to adjustits Tx beam when the base station uses a fixed Rx beam.

A UE may initiate a beam failure recovery (BFR) procedure based ondetecting a beam failure. The UE may transmit a BFR request (e.g., apreamble, a UCI, an SR, a MAC CE, and/or the like) based on theinitiating of the BFR procedure. The UE may detect the beam failurebased on a determination that a quality of beam pair link(s) of anassociated control channel is unsatisfactory (e.g., having an error ratehigher than an error rate threshold, a received signal power lower thana received signal power threshold, an expiration of a timer, and/or thelike).

The UE may measure a quality of a beam pair link using one or morereference signals (RSs) comprising one or more SS/PBCH blocks, one ormore CSI-RS resources, and/or one or more demodulation reference signals(DMRSs). A quality of the beam pair link may be based on one or more ofa block error rate (BLER), an RSRP value, a signal to interference plusnoise ratio (SINR) value, a reference signal received quality (RSRQ)value, and/or a CSI value measured on RS resources. The base station mayindicate that an RS resource is quasi co-located (QCLed) with one ormore DM-RSs of a channel (e.g., a control channel, a shared datachannel, and/or the like). The RS resource and the one or more DMRSs ofthe channel may be QCLed when the channel characteristics (e.g., Dopplershift, Doppler spread, average delay, delay spread, spatial Rxparameter, fading, and/or the like) from a transmission via the RSresource to the UE are similar or the same as the channelcharacteristics from a transmission via the channel to the UE.

A network (e.g., a gNB and/or an ng-eNB of a network) and/or the UE mayinitiate a random access procedure. A UE in an RRC_IDLE state and/or anRRC_INACTIVE state may initiate the random access procedure to request aconnection setup to a network. The UE may initiate the random accessprocedure from an RRC_CONNECTED state. The UE may initiate the randomaccess procedure to request uplink resources (e.g., for uplinktransmission of an SR when there is no PUCCH resource available) and/oracquire uplink timing (e.g., when uplink synchronization status isnon-synchronized). The UE may initiate the random access procedure torequest one or more system information blocks (SIBs) (e.g., other systeminformation such as SIB2, SIB3, and/or the like). The UE may initiatethe random access procedure for a beam failure recovery request. Anetwork may initiate a random access procedure for a handover and/or forestablishing time alignment for an SCell addition.

FIG. 13A illustrates a four-step contention-based random accessprocedure. Prior to initiation of the procedure, a base station maytransmit a configuration message 1310 to the UE. The procedureillustrated in FIG. 13A comprises transmission of four messages: a Msg 11311, a Msg 2 1312, a Msg 3 1313, and a Msg 4 1314. The Msg 1 1311 mayinclude and/or be referred to as a preamble (or a random accesspreamble). The Msg 2 1312 may include and/or be referred to as a randomaccess response (RAR).

The configuration message 1310 may be transmitted, for example, usingone or more RRC messages. The one or more RRC messages may indicate oneor more random access channel (RACH) parameters to the UE. The one ormore RACH parameters may comprise at least one of following: generalparameters for one or more random access procedures (e.g.,RACH-configGeneral); cell-specific parameters (e.g., RACH-ConfigCommon);and/or dedicated parameters (e.g., RACH-configDedicated). The basestation may broadcast or multicast the one or more RRC messages to oneor more UEs. The one or more RRC messages may be UE-specific (e.g.,dedicated RRC messages transmitted to a UE in an RRC_CONNECTED stateand/or in an RRC_INACTIVE state). The UE may determine, based on the oneor more RACH parameters, a time-frequency resource and/or an uplinktransmit power for transmission of the Msg 1 1311 and/or the Msg 3 1313.Based on the one or more RACH parameters, the UE may determine areception timing and a downlink channel for receiving the Msg 2 1312 andthe Msg 4 1314.

The one or more RACH parameters provided in the configuration message1310 may indicate one or more Physical RACH (PRACH) occasions availablefor transmission of the Msg 1 1311. The one or more PRACH occasions maybe predefined. The one or more RACH parameters may indicate one or moreavailable sets of one or more PRACH occasions (e.g., prach-ConfigIndex).The one or more RACH parameters may indicate an association between (a)one or more PRACH occasions and (b) one or more reference signals. Theone or more RACH parameters may indicate an association between (a) oneor more preambles and (b) one or more reference signals. The one or morereference signals may be SS/PBCH blocks and/or CSI-RSs. For example, theone or more RACH parameters may indicate a number of SS/PBCH blocksmapped to a PRACH occasion and/or a number of preambles mapped to aSS/PBCH blocks.

The one or more RACH parameters provided in the configuration message1310 may be used to determine an uplink transmit power of Msg 1 1311and/or Msg 3 1313. For example, the one or more RACH parameters mayindicate a reference power for a preamble transmission (e.g., a receivedtarget power and/or an initial power of the preamble transmission).There may be one or more power offsets indicated by the one or more RACHparameters. For example, the one or more RACH parameters may indicate: apower ramping step; a power offset between SSB and CSI-RS; a poweroffset between transmissions of the Msg 1 1311 and the Msg 3 1313;and/or a power offset value between preamble groups. The one or moreRACH parameters may indicate one or more thresholds based on which theUE may determine at least one reference signal (e.g., an SSB and/orCSI-RS) and/or an uplink carrier (e.g., a normal uplink (NUL) carrierand/or a supplemental uplink (SUL) carrier).

The Msg 1 1311 may include one or more preamble transmissions (e.g., apreamble transmission and one or more preamble retransmissions). An RRCmessage may be used to configure one or more preamble groups (e.g.,group A and/or group B). A preamble group may comprise one or morepreambles. The UE may determine the preamble group based on a pathlossmeasurement and/or a size of the Msg 3 1313. The UE may measure an RSRPof one or more reference signals (e.g., SSBs and/or CSI-RSs) anddetermine at least one reference signal having an RSRP above an RSRPthreshold (e.g., rsrp-ThresholdSSB and/or rsrp-ThresholdCSI-RS). The UEmay select at least one preamble associated with the one or morereference signals and/or a selected preamble group, for example, if theassociation between the one or more preambles and the at least onereference signal is configured by an RRC message.

The UE may determine the preamble based on the one or more RACHparameters provided in the configuration message 1310. For example, theUE may determine the preamble based on a pathloss measurement, an RSRPmeasurement, and/or a size of the Msg 3 1313. As another example, theone or more RACH parameters may indicate: a preamble format; a maximumnumber of preamble transmissions; and/or one or more thresholds fordetermining one or more preamble groups (e.g., group A and group B). Abase station may use the one or more RACH parameters to configure the UEwith an association between one or more preambles and one or morereference signals (e.g., SSBs and/or CSI-RSs). If the association isconfigured, the UE may determine the preamble to include in Msg 1 1311based on the association. The Msg 1 1311 may be transmitted to the basestation via one or more PRACH occasions. The UE may use one or morereference signals (e.g., SSBs and/or CSI-RSs) for selection of thepreamble and for determining of the PRACH occasion. One or more RACHparameters (e.g., ra-ssb-OccasionMskIndex and/or ra-OccasionList) mayindicate an association between the PRACH occasions and the one or morereference signals.

The UE may perform a preamble retransmission if no response is receivedfollowing a preamble transmission. The UE may increase an uplinktransmit power for the preamble retransmission. The UE may select aninitial preamble transmit power based on a pathloss measurement and/or atarget received preamble power configured by the network. The UE maydetermine to retransmit a preamble and may ramp up the uplink transmitpower. The UE may receive one or more RACH parameters (e.g.,PREAMBLE_POWER_RAMPING_STEP) indicating a ramping step for the preambleretransmission. The ramping step may be an amount of incrementalincrease in uplink transmit power for a retransmission. The UE may rampup the uplink transmit power if the UE determines a reference signal(e.g., SSB and/or CSI-RS) that is the same as a previous preambletransmission. The UE may count a number of preamble transmissions and/orretransmissions (e.g., PREAMBLE_TRANSMISSION_COUNTER). The UE maydetermine that a random access procedure completed unsuccessfully, forexample, if the number of preamble transmissions exceeds a thresholdconfigured by the one or more RACH parameters (e.g., preambleTransMax).

The Msg 2 1312 received by the UE may include an RAR. In some scenarios,the Msg 2 1312 may include multiple RARs corresponding to multiple UEs.The Msg 2 1312 may be received after or in response to the transmittingof the Msg 1 1311. The Msg 2 1312 may be scheduled on the DL-SCH andindicated on a PDCCH using a random access RNTI (RA-RNTI). The Msg 21312 may indicate that the Msg 1 1311 was received by the base station.The Msg 2 1312 may include a time-alignment command that may be used bythe UE to adjust the UE's transmission timing, a scheduling grant fortransmission of the Msg 3 1313, and/or a Temporary Cell RNTI (TC-RNTI).After transmitting a preamble, the UE may start a time window (e.g.,ra-ResponseWindow) to monitor a PDCCH for the Msg 2 1312. The UE maydetermine when to start the time window based on a PRACH occasion thatthe UE uses to transmit the preamble. For example, the UE may start thetime window one or more symbols after a last symbol of the preamble(e.g., at a first PDCCH occasion from an end of a preambletransmission). The one or more symbols may be determined based on anumerology. The PDCCH may be in a common search space (e.g., aType1-PDCCH common search space) configured by an RRC message. The UEmay identify the RAR based on a Radio Network Temporary Identifier(RNTI). RNTIs may be used depending on one or more events initiating therandom access procedure. The UE may use random access RNTI (RA-RNTI).The RA-RNTI may be associated with PRACH occasions in which the UEtransmits a preamble. For example, the UE may determine the RA-RNTIbased on: an OFDM symbol index; a slot index; a frequency domain index;and/or a UL carrier indicator of the PRACH occasions. An example ofRA-RNTI may be as follows:RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_idwhere s_id may be an index of a first OFDM symbol of the PRACH occasion(e.g., 0≤s_id<14), t_id may be an index of a first slot of the PRACHoccasion in a system frame (e.g., 0≤t_id<80), f_id may be an index ofthe PRACH occasion in the frequency domain (e.g., 0≤f_id<8), andul_carrier_id may be a UL carrier used for a preamble transmission(e.g., 0 for an NUL carrier, and 1 for an SUL carrier).The UE may transmit the Msg 3 1313 in response to a successful receptionof the Msg 2 1312 (e.g., using resources identified in the Msg 2 1312).The Msg 3 1313 may be used for contention resolution in, for example,the contention-based random access procedure illustrated in FIG. 13A. Insome scenarios, a plurality of UEs may transmit a same preamble to abase station and the base station may provide an RAR that corresponds toa UE. Collisions may occur if the plurality of UEsinterpret the RAR ascorresponding to themselves. Contention resolution (e.g., using the Msg3 1313 and the Msg 4 1314) may be used to increase the likelihood thatthe UE does not incorrectly use an identity of another the UE. Toperform contention resolution, the UE may include a device identifier inthe Msg 3 1313 (e.g., a C-RNTI if assigned, a TC RNTI included in theMsg 2 1312, and/or any other suitable identifier).

The Msg 4 1314 may be received after or in response to the transmittingof the Msg 3 1313. If a C-RNTI was included in the Msg 3 1313, the basestation will address the UE on the PDCCH using the C-RNTI. If the UE'sunique C-RNTI is detected on the PDCCH, the random access procedure isdetermined to be successfully completed. If a TC-RNTI is included in theMsg 3 1313 (e.g., if the UE is in an RRC_IDLE state or not otherwiseconnected to the base station), Msg 4 1314 will be received using aDL-SCH associated with the TC-RNTI. If a MAC PDU is successfully decodedand a MAC PDU comprises the UE contention resolution identity MAC CEthat matches or otherwise corresponds with the CCCH SDU sent (e.g.,transmitted) in Msg 3 1313, the UE may determine that the contentionresolution is successful and/or the UE may determine that the randomaccess procedure is successfully completed.

The UE may be configured with a supplementary uplink (SUL) carrier and anormal uplink (NUL) carrier. An initial access (e.g., random accessprocedure) may be supported in an uplink carrier. For example, a basestation may configure the UE with two separate RACH configurations: onefor an SUL carrier and the other for an NUL carrier. For random accessin a cell configured with an SUL carrier, the network may indicate whichcarrier to use (NUL or SUL). The UE may determine the SUL carrier, forexample, if a measured quality of one or more reference signals is lowerthan a broadcast threshold. Uplink transmissions of the random accessprocedure (e.g., the Msg 1 1311 and/or the Msg 3 1313) may remain on theselected carrier. The UE may switch an uplink carrier during the randomaccess procedure (e.g., between the Msg 1 1311 and the Msg 3 1313) inone or more cases. For example, the UE may determine and/or switch anuplink carrier for the Msg 1 1311 and/or the Msg 3 1313 based on achannel clear assessment (e.g., a listen-before-talk).

FIG. 13B illustrates a two-step contention-free random access procedure.Similar to the four-step contention-based random access procedureillustrated in FIG. 13A, a base station may, prior to initiation of theprocedure, transmit a configuration message 1320 to the UE. Theconfiguration message 1320 may be analogous in some respects to theconfiguration message 1310. The procedure illustrated in FIG. 13Bcomprises transmission of two messages: a Msg 1 1321 and a Msg 2 1322.The Msg 1 1321 and the Msg 2 1322 may be analogous in some respects tothe Msg 1 1311 and a Msg 2 1312 illustrated in FIG. 13A, respectively.As will be understood from FIGS. 13A and 13B, the contention-free randomaccess procedure may not include messages analogous to the Msg 3 1313and/or the Msg 4 1314.

The contention-free random access procedure illustrated in FIG. 13B maybe initiated for a beam failure recovery, other SI request, SCelladdition, and/or handover. For example, a base station may indicate orassign to the UE the preamble to be used for the Msg 1 1321. The UE mayreceive, from the base station via PDCCH and/or RRC, an indication of apreamble (e.g., ra-PreambleIndex).

After transmitting a preamble, the UE may start a time window (e.g.,ra-ResponseWindow) to monitor a PDCCH for the RAR. In the event of abeam failure recovery request, the base station may configure the UEwith a separate time window and/or a separate PDCCH in a search spaceindicated by an RRC message (e.g., recoverySearchSpaceId). The UE maymonitor for a PDCCH transmission addressed to a Cell RNTI (C-RNTI) onthe search space. In the contention-free random access procedureillustrated in FIG. 13B, the UE may determine that a random accessprocedure successfully completes after or in response to transmission ofMsg 1 1321 and reception of a corresponding Msg 2 1322. The UE maydetermine that a random access procedure successfully completes, forexample, if a PDCCH transmission is addressed to a C-RNTI. The UE maydetermine that a random access procedure successfully completes, forexample, if the UE receives an RAR comprising a preamble identifiercorresponding to a preamble transmitted by the UE and/or the RARcomprises a MAC sub-PDU with the preamble identifier. The UE maydetermine the response as an indication of an acknowledgement for an SIrequest.

FIG. 13C illustrates another two-step random access procedure. Similarto the random access procedures illustrated in FIGS. 13A and 13B, a basestation may, prior to initiation of the procedure, transmit aconfiguration message 1330 to the UE. The configuration message 1330 maybe analogous in some respects to the configuration message 1310 and/orthe configuration message 1320. The procedure illustrated in FIG. 13Ccomprises transmission of two messages: a Msg A 1331 and a Msg B 1332.

Msg A 1331 may be transmitted in an uplink transmission by the UE. Msg A1331 may comprise one or more transmissions of a preamble 1341 and/orone or more transmissions of a transport block 1342. The transport block1342 may comprise contents that are similar and/or equivalent to thecontents of the Msg 3 1313 illustrated in FIG. 13A. The transport block1342 may comprise UCI (e.g., an SR, a HARQ ACK/NACK, and/or the like).The UE may receive the Msg B 1332 after or in response to transmittingthe Msg A 1331. The Msg B 1332 may comprise contents that are similarand/or equivalent to the contents of the Msg 2 1312 (e.g., an RAR)illustrated in FIGS. 13A and 13B and/or the Msg 4 1314 illustrated inFIG. 13A.

The UE may initiate the two-step random access procedure in FIG. 13C forlicensed spectrum and/or unlicensed spectrum. The UE may determine,based on one or more factors, whether to initiate the two-step randomaccess procedure. The one or more factors may be: a radio accesstechnology in use (e.g., LTE, NR, and/or the like); whether the UE hasvalid TA or not; a cell size; the UE's RRC state; a type of spectrum(e.g., licensed vs. unlicensed); and/or any other suitable factors.

The UE may determine, based on two-step RACH parameters included in theconfiguration message 1330, a radio resource and/or an uplink transmitpower for the preamble 1341 and/or the transport block 1342 included inthe Msg A 1331. The RACH parameters may indicate a modulation and codingschemes (MCS), a time-frequency resource, and/or a power control for thepreamble 1341 and/or the transport block 1342. A time-frequency resourcefor transmission of the preamble 1341 (e.g., a PRACH) and atime-frequency resource for transmission of the transport block 1342(e.g., a PUSCH) may be multiplexed using FDM, TDM, and/or CDM. The RACHparameters may enable the UE to determine a reception timing and adownlink channel for monitoring for and/or receiving Msg B 1332.

The transport block 1342 may comprise data (e.g., delay-sensitive data),an identifier of the UE, security information, and/or device information(e.g., an International Mobile Subscriber Identity (IMSI)). The basestation may transmit the Msg B 1332 as a response to the Msg A 1331. TheMsg B 1332 may comprise at least one of following: a preambleidentifier; a timing advance command; a power control command; an uplinkgrant (e.g., a radio resource assignment and/or an MCS); a UE identifierfor contention resolution; and/or an RNTI (e.g., a C-RNTI or a TC-RNTI).The UE may determine that the two-step random access procedure issuccessfully completed if: a preamble identifier in the Msg B 1332 ismatched to a preamble transmitted by the UE; and/or the identifier ofthe UE in Msg B 1332 is matched to the identifier of the UE in the Msg A1331 (e.g., the transport block 1342).

A UE and a base station may exchange control signaling. The controlsignaling may be referred to as L1/L2 control signaling and mayoriginate from the PHY layer (e.g., layer 1) and/or the MAC layer (e.g.,layer 2). The control signaling may comprise downlink control signalingtransmitted from the base station to the UE and/or uplink controlsignaling transmitted from the UE to the base station.

The downlink control signaling may comprise: a downlink schedulingassignment; an uplink scheduling grant indicating uplink radio resourcesand/or a transport format; a slot format information; a preemptionindication; a power control command; and/or any other suitablesignaling. The UE may receive the downlink control signaling in apayload transmitted by the base station on a physical downlink controlchannel (PDCCH). The payload transmitted on the PDCCH may be referred toas downlink control information (DCI). In some scenarios, the PDCCH maybe a group common PDCCH (GC-PDCCH) that is common to a group of UEs.

A base station may attach one or more cyclic redundancy check (CRC)parity bits to a DCI in order to facilitate detection of transmissionerrors. When the DCI is intended for a UE (or a group of the UEs), thebase station may scramble the CRC parity bits with an identifier of theUE (or an identifier of the group of the UEs). Scrambling the CRC paritybits with the identifier may comprise Modulo-2 addition (or an exclusiveOR operation) of the identifier value and the CRC parity bits. Theidentifier may comprise a 16-bit value of a radio network temporaryidentifier (RNTI).

DCIs may be used for different purposes. A purpose may be indicated bythe type of RNTI used to scramble the CRC parity bits. For example, aDCI having CRC parity bits scrambled with a paging RNTI (P-RNTI) mayindicate paging information and/or a system information changenotification. The P-RNTI may be predefined as “FFFE” in hexadecimal. ADCI having CRC parity bits scrambled with a system information RNTI(SI-RNTI) may indicate a broadcast transmission of the systeminformation. The SI-RNTI may be predefined as “FFFF” in hexadecimal. ADCI having CRC parity bits scrambled with a random access RNTI (RA-RNTI)may indicate a random access response (RAR). A DCI having CRC paritybits scrambled with a cell RNTI (C-RNTI) may indicate a dynamicallyscheduled unicast transmission and/or a triggering of PDCCH-orderedrandom access. A DCI having CRC parity bits scrambled with a temporarycell RNTI (TC-RNTI) may indicate a contention resolution (e.g., a Msg 3analogous to the Msg 3 1313 illustrated in FIG. 13A). Other RNTIsconfigured to the UE by a base station may comprise a ConfiguredScheduling RNTI (CS-RNTI), a Transmit Power Control-PUCCH RNTI(TPC-PUCCH-RNTI), a Transmit Power Control-PUSCH RNTI (TPC-PUSCH-RNTI),a Transmit Power Control-SRS RNTI (TPC-SRS-RNTI), an Interruption RNTI(INT-RNTI), a Slot Format Indication RNTI (SFI-RNTI), a Semi-PersistentCSI RNTI (SP-CSI-RNTI), a Modulation and Coding Scheme Cell RNTI(MCS-C-RNTI), and/or the like.

Depending on the purpose and/or content of a DCI, the base station maytransmit the DCIs with one or more DCI formats. For example, DCI format0_0 may be used for scheduling of PUSCH in a cell. DCI format 0_0 may bea fallback DCI format (e.g., with compact DCI payloads). DCI format 0_1may be used for scheduling of PUSCH in a cell (e.g., with more DCIpayloads than DCI format 0_0). DCI format 1_0 may be used for schedulingof PDSCH in a cell. DCI format 1_0 may be a fallback DCI format (e.g.,with compact DCI payloads). DCI format 1_1 may be used for scheduling ofPDSCH in a cell (e.g., with more DCI payloads than DCI format 1_0). DCIformat 2_0 may be used for providing a slot format indication to a groupof UEs. DCI format 2_1 may be used for notifying a group of UEs of aphysical resource block and/or OFDM symbol where the UE may assume notransmission is intended to the UE. DCI format 2_2 may be used fortransmission of a transmit power control (TPC) command for PUCCH orPUSCH. DCI format 2_3 may be used for transmission of a group of TPCcommands for SRS transmissions by one or more UEs. DCI format(s) for newfunctions may be defined in future releases. DCI formats may havedifferent DCI sizes, or may share the same DCI size.

After scrambling a DCI with a RNTI, the base station may process the DCIwith channel coding (e.g., polar coding), rate matching, scramblingand/or QPSK modulation. A base station may map the coded and modulatedDCI on resource elements used and/or configured for a PDCCH. Based on apayload size of the DCI and/or a coverage of the base station, the basestation may transmit the DCI via a PDCCH occupying a number ofcontiguous control channel elements (CCEs). The number of the contiguousCCEs (referred to as aggregation level) may be 1, 2, 4, 8, 16, and/orany other suitable number. A CCE may comprise a number (e.g., 6) ofresource-element groups (REGs). A REG may comprise a resource block inan OFDM symbol. The mapping of the coded and modulated DCI on theresource elements may be based on mapping of CCEs and REGs (e.g.,CCE-to-REG mapping).

FIG. 14A illustrates an example of CORESET configurations for abandwidth part. The base station may transmit a DCI via a PDCCH on oneor more control resource sets (CORESETs). A CORESET may comprise atime-frequency resource in which the UE tries to decode a DCI using oneor more search spaces. The base station may configure a CORESET in thetime-frequency domain. In the example of FIG. 14A, a first CORESET 1401and a second CORESET 1402 occur at the first symbol in a slot. The firstCORESET 1401 overlaps with the second CORESET 1402 in the frequencydomain. A third CORESET 1403 occurs at a third symbol in the slot. Afourth CORESET 1404 occurs at the seventh symbol in the slot. CORESETsmay have a different number of resource blocks in frequency domain.

FIG. 14B illustrates an example of a CCE-to-REG mapping for DCItransmission on a CORESET and PDCCH processing. The CCE-to-REG mappingmay be an interleaved mapping (e.g., for the purpose of providingfrequency diversity) or a non-interleaved mapping (e.g., for thepurposes of facilitating interference coordination and/orfrequency-selective transmission of control channels). The base stationmay perform different or same CCE-to-REG mapping on different CORESETs.A CORESET may be associated with a CCE-to-REG mapping by RRCconfiguration. A CORESET may be configured with an antenna port quasico-location (QCL) parameter. The antenna port QCL parameter may indicateQCL information of a demodulation reference signal (DMRS) for PDCCHreception in the CORESET.

The base station may transmit, to the UE, RRC messages comprisingconfiguration parameters of one or more CORESETs and one or more searchspace sets. The configuration parameters may indicate an associationbetween a search space set and a CORESET. A search space set maycomprise a set of PDCCH candidates formed by CCEs at a given aggregationlevel. The configuration parameters may indicate: a number of PDCCHcandidates to be monitored per aggregation level; a PDCCH monitoringperiodicity and a PDCCH monitoring pattern; one or more DCI formats tobe monitored by the UE; and/or whether a search space set is a commonsearch space set or a UE-specific search space set. A set of CCEs in thecommon search space set may be predefined and known to the UE. A set ofCCEs in the UE-specific search space set may be configured based on theUE's identity (e.g., C-RNTI).

As shown in FIG. 14B, the UE may determine a time-frequency resource fora CORESET based on RRC messages. The UE may determine a CCE-to-REGmapping (e.g., interleaved or non-interleaved, and/or mappingparameters) for the CORESET based on configuration parameters of theCORESET. The UE may determine a number (e.g., at most 10) of searchspace sets configured on the CORESET based on the RRC messages. The UEmay monitor a set of PDCCH candidates according to configurationparameters of a search space set. The UE may monitor a set of PDCCHcandidates in one or more CORESETs for detecting one or more DCIs.Monitoring may comprise decoding one or more PDCCH candidates of the setof the PDCCH candidates according to the monitored DCI formats.Monitoring may comprise decoding a DCI content of one or more PDCCHcandidates with possible (or configured) PDCCH locations, possible (orconfigured) PDCCH formats (e.g., number of CCEs, number of PDCCHcandidates in common search spaces, and/or number of PDCCH candidates inthe UE-specific search spaces) and possible (or configured) DCI formats.The decoding may be referred to as blind decoding. The UE may determinea DCI as valid for the UE, in response to CRC checking (e.g., scrambledbits for CRC parity bits of the DCI matching a RNTI value). The UE mayprocess information contained in the DCI (e.g., a scheduling assignment,an uplink grant, power control, a slot format indication, a downlinkpreemption, and/or the like).

The UE may transmit uplink control signaling (e.g., uplink controlinformation (UCI)) to a base station. The uplink control signaling maycomprise hybrid automatic repeat request (HARQ) acknowledgements forreceived DL-SCH transport blocks. The UE may transmit the HARQacknowledgements after receiving a DL-SCH transport block. Uplinkcontrol signaling may comprise channel state information (CSI)indicating channel quality of a physical downlink channel. The UE maytransmit the CSI to the base station. The base station, based on thereceived CSI, may determine transmission format parameters (e.g.,comprising multi-antenna and beamforming schemes) for a downlinktransmission. Uplink control signaling may comprise scheduling requests(SR). The UE may transmit an SR indicating that uplink data is availablefor transmission to the base station. The UE may transmit a UCI (e.g.,HARQ acknowledgements (HARQ-ACK), CSI report, SR, and the like) via aphysical uplink control channel (PUCCH) or a physical uplink sharedchannel (PUSCH). The UE may transmit the uplink control signaling via aPUCCH using one of several PUCCH formats.

There may be five PUCCH formats and the UE may determine a PUCCH formatbased on a size of the UCI (e.g., a number of uplink symbols of UCItransmission and a number of UCI bits). PUCCH format 0 may have a lengthof one or two OFDM symbols and may include two or fewer bits. The UE maytransmit UCI in a PUCCH resource using PUCCH format 0 if thetransmission is over one or two symbols and the number of HARQ-ACKinformation bits with positive or negative SR (HARQ-ACK/SR bits) is oneor two. PUCCH format 1 may occupy a number between four and fourteenOFDM symbols and may include two or fewer bits. The UE may use PUCCHformat 1 if the transmission is four or more symbols and the number ofHARQ-ACK/SR bits is one or two. PUCCH format 2 may occupy one or twoOFDM symbols and may include more than two bits. The UE may use PUCCHformat 2 if the transmission is over one or two symbols and the numberof UCI bits is two or more. PUCCH format 3 may occupy a number betweenfour and fourteen OFDM symbols and may include more than two bits. TheUE may use PUCCH format 3 if the transmission is four or more symbols,the number of UCI bits is two or more and PUCCH resource does notinclude an orthogonal cover code. PUCCH format 4 may occupy a numberbetween four and fourteen OFDM symbols and may include more than twobits. The UE may use PUCCH format 4 if the transmission is four or moresymbols, the number of UCI bits is two or more and the PUCCH resourceincludes an orthogonal cover code.

The base station may transmit configuration parameters to the UE for aplurality of PUCCH resource sets using, for example, an RRC message. Theplurality of PUCCH resource sets (e.g., up to four sets) may beconfigured on an uplink BWP of a cell. A PUCCH resource set may beconfigured with a PUCCH resource set index, a plurality of PUCCHresources with a PUCCH resource being identified by a PUCCH resourceidentifier (e.g., pucch-Resourceid), and/or a number (e.g. a maximumnumber) of UCI information bits the UE may transmit using one of theplurality of PUCCH resources in the PUCCH resource set. When configuredwith a plurality of PUCCH resource sets, the UE may select one of theplurality of PUCCH resource sets based on a total bit length of the UCIinformation bits (e.g., HARQ-ACK, SR, and/or CSI). If the total bitlength of UCI information bits is two or fewer, the UE may select afirst PUCCH resource set having a PUCCH resource set index equal to “0”.If the total bit length of UCI information bits is greater than two andless than or equal to a first configured value, the UE may select asecond PUCCH resource set having a PUCCH resource set index equal to“1”. If the total bit length of UCI information bits is greater than thefirst configured value and less than or equal to a second configuredvalue, the UE may select a third PUCCH resource set having a PUCCHresource set index equal to “2”. If the total bit length of UCIinformation bits is greater than the second configured value and lessthan or equal to a third value (e.g., 1406), the UE may select a fourthPUCCH resource set having a PUCCH resource set index equal to “3”.

After determining a PUCCH resource set from a plurality of PUCCHresource sets, the UE may determine a PUCCH resource from the PUCCHresource set for UCI (HARQ-ACK, CSI, and/or SR) transmission. The UE maydetermine the PUCCH resource based on a PUCCH resource indicator in aDCI (e.g., with a DCI format 1_0 or DCI for 1_1) received on a PDCCH. Athree-bit PUCCH resource indicator in the DCI may indicate one of eightPUCCH resources in the PUCCH resource set. Based on the PUCCH resourceindicator, the UE may transmit the UCI (HARQ-ACK, CSI and/or SR) using aPUCCH resource indicated by the PUCCH resource indicator in the DCI.

FIG. 15 illustrates an example of a wireless device 1502 incommunication with a base station 1504 in accordance with embodiments ofthe present disclosure. The wireless device 1502 and base station 1504may be part of a mobile communication network, such as the mobilecommunication network 100 illustrated in FIG. 1A, the mobilecommunication network 150 illustrated in FIG. 1B, or any othercommunication network. Only one wireless device 1502 and one basestation 1504 are illustrated in FIG. 15 , but it will be understood thata mobile communication network may include more than one UE and/or morethan one base station, with the same or similar configuration as thoseshown in FIG. 15 .

The base station 1504 may connect the wireless device 1502 to a corenetwork (not shown) through radio communications over the air interface(or radio interface) 1506. The communication direction from the basestation 1504 to the wireless device 1502 over the air interface 1506 isknown as the downlink, and the communication direction from the wirelessdevice 1502 to the base station 1504 over the air interface is known asthe uplink. Downlink transmissions may be separated from uplinktransmissions using FDD, TDD, and/or some combination of the twoduplexing techniques.

In the downlink, data to be sent to the wireless device 1502 from thebase station 1504 may be provided to the processing system 1508 of thebase station 1504. The data may be provided to the processing system1508 by, for example, a core network. In the uplink, data to be sent tothe base station 1504 from the wireless device 1502 may be provided tothe processing system 1518 of the wireless device 1502. The processingsystem 1508 and the processing system 1518 may implement layer 3 andlayer 2 OSI functionality to process the data for transmission. Layer 2may include an SDAP layer, a PDCP layer, an RLC layer, and a MAC layer,for example, with respect to FIG. 2A, FIG. 2B, FIG. 3 , and FIG. 4A.Layer 3 may include an RRC layer as with respect to FIG. 2B.

After being processed by processing system 1508, the data to be sent tothe wireless device 1502 may be provided to a transmission processingsystem 1510 of base station 1504. Similarly, after being processed bythe processing system 1518, the data to be sent to base station 1504 maybe provided to a transmission processing system 1520 of the wirelessdevice 1502. The transmission processing system 1510 and thetransmission processing system 1520 may implement layer 1 OSIfunctionality. Layer 1 may include a PHY layer with respect to FIG. 2A,FIG. 2B, FIG. 3 , and FIG. 4A. For transmit processing, the PHY layermay perform, for example, forward error correction coding of transportchannels, interleaving, rate matching, mapping of transport channels tophysical channels, modulation of physical channel, multiple-inputmultiple-output (MIMO) or multi-antenna processing, and/or the like.

At the base station 1504, a reception processing system 1512 may receivethe uplink transmission from the wireless device 1502. At the wirelessdevice 1502, a reception processing system 1522 may receive the downlinktransmission from base station 1504. The reception processing system1512 and the reception processing system 1522 may implement layer 1 OSIfunctionality. Layer 1 may include a PHY layer with respect to FIG. 2A,FIG. 2B, FIG. 3 , and FIG. 4A. For receive processing, the PHY layer mayperform, for example, error detection, forward error correctiondecoding, deinterleaving, demapping of transport channels to physicalchannels, demodulation of physical channels, MIMO or multi-antennaprocessing, and/or the like.

As shown in FIG. 15 , a wireless device 1502 and the base station 1504may include multiple antennas. The multiple antennas may be used toperform one or more MIMO or multi-antenna techniques, such as spatialmultiplexing (e.g., single-user MIMO or multi-user MIMO),transmit/receive diversity, and/or beamforming. In other examples, thewireless device 1502 and/or the base station 1504 may have a singleantenna.

The processing system 1508 and the processing system 1518 maybeassociated with a memory 1514 and a memory 1524, respectively. Memory1514 and memory 1524 (e.g., one or more non-transitory computer readablemediums) may store computer program instructions or code that may beexecuted by the processing system 1508 and/or the processing system 1518to carry out one or more of the functionalities discussed in the presentapplication. Although not shown in FIG. 15 , the transmission processingsystem 1510, the transmission processing system 1520, the receptionprocessing system 1512, and/or the reception processing system 1522 maybe coupled to a memory (e.g., one or more non-transitory computerreadable mediums) storing computer program instructions or code that maybe executed to carry out one or more of their respectivefunctionalities.

The processing system 1508 and/or the processing system 1518 maycomprise one or more controllers and/or one or more processors. The oneor more controllers and/or one or more processors may comprise, forexample, a general-purpose processor, a digital signal processor (DSP),a microcontroller, an application specific integrated circuit (ASIC), afield programmable gate array (FPGA) and/or other programmable logicdevice, discrete gate and/or transistor logic, discrete hardwarecomponents, an on-board unit, or any combination thereof. The processingsystem 1508 and/or the processing system 1518 may perform at least oneof signal coding/processing, data processing, power control,input/output processing, and/or any other functionality that may enablethe wireless device 1502 and the base station 1504 to operate in awireless environment.

The processing system 1508 and/or the processing system 1518 may beconnected to one or more peripherals 1516 and one or more peripherals1526, respectively. The one or more peripherals 1516 and the one or moreperipherals 1526 may include software and/or hardware that providefeatures and/or functionalities, for example, a speaker, a microphone, akeypad, a display, a touchpad, a power source, a satellite transceiver,a universal serial bus (USB) port, a hands-free headset, a frequencymodulated (FM) radio unit, a media player, an Internet browser, anelectronic control unit (e.g., for a motor vehicle), and/or one or moresensors (e.g., an accelerometer, a gyroscope, a temperature sensor, aradar sensor, a lidar sensor, an ultrasonic sensor, a light sensor, acamera, and/or the like). The processing system 1508 and/or theprocessing system 1518 may receive user input data from and/or provideuser output data to the one or more peripherals 1516 and/or the one ormore peripherals 1526. The processing system 1518 in the wireless device1502 may receive power from a power source and/or may be configured todistribute the power to the other components in the wireless device1502. The power source may comprise one or more sources of power, forexample, a battery, a solar cell, a fuel cell, or any combinationthereof. The processing system 1508 and/or the processing system 1518may be connected to a GPS chipset 1517 and a GPS chipset 1527,respectively. The GPS chipset 1517 and the GPS chipset 1527 may beconfigured to provide geographic location information of the wirelessdevice 1502 and the base station 1504, respectively.

FIG. 16A illustrates an example structure for uplink transmission. Abaseband signal representing a physical uplink shared channel mayperform one or more functions. The one or more functions may comprise atleast one of: scrambling; modulation of scrambled bits to generatecomplex-valued symbols; mapping of the complex-valued modulation symbolsonto one or several transmission layers; transform precoding to generatecomplex-valued symbols; precoding of the complex-valued symbols; mappingof precoded complex-valued symbols to resource elements; generation ofcomplex-valued time-domain Single Carrier-Frequency Division MultipleAccess (SC-FDMA) or CP-OFDM signal for an antenna port; and/or the like.In an example, when transform precoding is enabled, a SC-FDMA signal foruplink transmission may be generated. In an example, when transformprecoding is not enabled, an CP-OFDM signal for uplink transmission maybe generated by FIG. 16A. These functions are illustrated as examplesand it is anticipated that other mechanisms may be implemented invarious embodiments.

FIG. 16B illustrates an example structure for modulation andup-conversion of a baseband signal to a carrier frequency. The basebandsignal may be a complex-valued SC-FDMA or CP-OFDM baseband signal for anantenna port and/or a complex-valued Physical Random Access Channel(PRACH) baseband signal. Filtering may be employed prior totransmission.

FIG. 16C illustrates an example structure for downlink transmissions. Abaseband signal representing a physical downlink channel may perform oneor more functions. The one or more functions may comprise: scrambling ofcoded bits in a codeword to be transmitted on a physical channel;modulation of scrambled bits to generate complex-valued modulationsymbols; mapping of the complex-valued modulation symbols onto one orseveral transmission layers; precoding of the complex-valued modulationsymbols on a layer for transmission on the antenna ports; mapping ofcomplex-valued modulation symbols for an antenna port to resourceelements; generation of complex-valued time-domain OFDM signal for anantenna port; and/or the like. These functions are illustrated asexamples and it is anticipated that other mechanisms may be implementedin various embodiments.

FIG. 16D illustrates another example structure for modulation andup-conversion of a baseband signal to a carrier frequency. The basebandsignal may be a complex-valued OFDM baseband signal for an antenna port.Filtering may be employed prior to transmission.

A wireless device may receive from a base station one or more messages(e.g. RRC messages) comprising configuration parameters of a pluralityof cells (e.g. primary cell, secondary cell). The wireless device maycommunicate with at least one base station (e.g. two or more basestations in dual-connectivity) via the plurality of cells. The one ormore messages (e.g. as a part of the configuration parameters) maycomprise parameters of physical, MAC, RLC, PCDP, SDAP, RRC layers forconfiguring the wireless device. For example, the configurationparameters may comprise parameters for configuring physical and MAClayer channels, bearers, etc. For example, the configuration parametersmay comprise parameters indicating values of timers for physical, MAC,RLC, PCDP, SDAP, RRC layers, and/or communication channels.

A timer may begin running once it is started and continue running untilit is stopped or until it expires. A timer may be started if it is notrunning or restarted if it is running. A timer may be associated with avalue (e.g. the timer may be started or restarted from a value or may bestarted from zero and expire once it reaches the value). The duration ofa timer may not be updated until the timer is stopped or expires (e.g.,due to BWP switching). A timer may be used to measure a timeperiod/window for a process. When the specification refers to animplementation and procedure related to one or more timers, it will beunderstood that there are multiple ways to implement the one or moretimers. For example, it will be understood that one or more of themultiple ways to implement a timer may be used to measure a timeperiod/window for the procedure. For example, a random access responsewindow timer may be used for measuring a window of time for receiving arandom access response. In an example, instead of starting and expiry ofa random access response window timer, the time difference between twotime stamps may be used. When a timer is restarted, a process formeasurement of time window may be restarted. Other exampleimplementations may be provided to restart a measurement of a timewindow.

A gNB may transmit one or more MAC PDUs to a wireless device. In anexample, a MAC PDU may be a bit string that is byte aligned (e.g., amultiple of eight bits) in length. In an example, bit strings may berepresented by tables in which the most significant bit is the leftmostbit of the first line of the table, and the least significant bit is therightmost bit on the last line of the table. More generally, the bitstring may be read from left to right and then in the reading order ofthe lines. In an example, the bit order of a parameter field within aMAC PDU is represented with the first and most significant bit in theleftmost bit and the last and least significant bit in the rightmostbit.

In an example, a MAC SDU may be a bit string that is byte aligned (e.g.,a multiple of eight bits) in length. In an example, a MAC SDU may beincluded in a MAC PDU from the first bit onward. A MAC CE may be a bitstring that is byte aligned (e.g., a multiple of eight bits) in length.A MAC subheader may be a bit string that is byte aligned (e.g., amultiple of eight bits) in length. In an example, a MAC subheader may beplaced immediately in front of a corresponding MAC SDU, MAC CE, orpadding. A MAC entity may ignore a value of reserved bits in a DL MACPDU.

In an example, a MAC PDU may comprise one or more MAC subPDUs. A MACsubPDU of the one or more MAC subPDUs may comprise: a MAC subheader only(including padding); a MAC subheader and a MAC SDU; a MAC subheader anda MAC CE; and/or a MAC subheader and padding. The MAC SDU may be ofvariable size. A MAC subheader may correspond to a MAC SDU, a MAC CE, orpadding.

In an example, when a MAC subheader corresponds to a MAC SDU, avariable-sized MAC CE, or padding, the MAC subheader may comprise: an Rfield with a one bit length; an F field with a one bit length; an LCIDfield with a multi-bit length; and/or an L field with a multi-bitlength.

FIG. 17A shows an example of a MAC subheader with an R field, an Ffield, an LCID field, and an L field. In the example MAC subheader ofFIG. 17A, the LCID field may be six bits in length, and the L field maybe eight bits in length. FIG. 17B shows example of a MAC subheader withan R field, a F field, an LCID field, and an L field. In the example MACsubheader of FIG. 17B, the LCID field may be six bits in length, and theL field may be sixteen bits in length. When a MAC subheader correspondsto a fixed sized MAC CE or padding, the MAC subheader may comprise: an Rfield with a two bit length and an LCID field with a multi-bit length.FIG. 17C shows an example of a MAC subheader with an R field and an LCIDfield. In the example MAC subheader of FIG. 17C, the LCID field may besix bits in length, and the R field may be two bits in length.

FIG. 18A shows an example of a DL MAC PDU. Multiple MAC CEs, such as MACCE 1 and 2, may be placed together. A MAC subPDU comprising a MAC CE maybe placed before any MAC subPDU comprising a MAC SDU or a MAC subPDUcomprising padding. FIG. 18B shows an example of a UL MAC PDU. MultipleMAC CEs, such as MAC CE 1 and 2, may be placed together. A MAC subPDUcomprising a MAC CE may be placed after all MAC subPDUs comprising a MACSDU. In addition, the MAC subPDU may be placed before a MAC subPDUcomprising padding.

In an example, a MAC entity of a gNB may transmit one or more MAC CEs toa MAC entity of a wireless device. FIG. 19 shows an example of multipleLCIDs that may be associated with the one or more MAC CEs. The one ormore MAC CEs comprise at least one of: a SP ZP CSI-RS Resource SetActivation/Deactivation MAC CE, a PUCCH spatial relationActivation/Deactivation MAC CE, a SP SRS Activation/Deactivation MAC CE,a SP CSI reporting on PUCCH Activation/Deactivation MAC CE, a TCI StateIndication for UE-specific PDCCH MAC CE, a TCI State Indication forUE-specific PDSCH MAC CE, an Aperiodic CSI Trigger State SubselectionMAC CE, a SP CSI-RS/CSI-IM Resource Set Activation/Deactivation MAC CE,a UE contention resolution identity MAC CE, a timing advance command MACCE, a DRX command MAC CE, a Long DRX command MAC CE, an SCellactivation/deactivation MAC CE (1 Octet), an SCellactivation/deactivation MAC CE (4 Octet), and/or a duplicationactivation/deactivation MAC CE. In an example, a MAC CE, such as a MACCE transmitted by a MAC entity of a gNB to a MAC entity of a wirelessdevice, may have an LCID in the MAC subheader corresponding to the MACCE. Different MAC CE may have different LCID in the MAC subheadercorresponding to the MAC CE. For example, an LCID given by 111011 in aMAC subheader may indicate that a MAC CE associated with the MACsubheader is a long DRX command MAC CE.

In an example, the MAC entity of the wireless device may transmit to theMAC entity of the gNB one or more MAC CEs. FIG. 20 shows an example ofthe one or more MAC CEs. The one or more MAC CEs may comprise at leastone of: a short buffer status report (BSR) MAC CE, a long BSR MAC CE, aC-RNTI MAC CE, a configured grant confirmation MAC CE, a single entryPHR MAC CE, a multiple entry PHR MAC CE, a short truncated BSR, and/or along truncated BSR. In an example, a MAC CE may have an LCID in the MACsubheader corresponding to the MAC CE. Different MAC CE may havedifferent LCID in the MAC subheader corresponding to the MAC CE. Forexample, an LCID given by 111011 in a MAC subheader may indicate that aMAC CE associated with the MAC subheader is a short-truncated commandMAC CE.

In carrier aggregation (CA), two or more component carriers (CCs) may beaggregated. A wireless device may simultaneously receive or transmit onone or more CCs, depending on capabilities of the wireless device, usingthe technique of CA. In an example, a wireless device may support CA forcontiguous CCs and/or for non-contiguous CCs. CCs may be organized intocells. For example, CCs may be organized into one primary cell (PCell)and one or more secondary cells (SCells). When configured with CA, awireless device may have one RRC connection with a network. During anRRC connection establishment/re-establishment/handover, a cell providingNAS mobility information may be a serving cell. During an RRC connectionre-establishment/handover procedure, a cell providing a security inputmay be a serving cell. In an example, the serving cell may denote aPCell. In an example, a gNB may transmit, to a wireless device, one ormore messages comprising configuration parameters of a plurality of oneor more SCells, depending on capabilities of the wireless device.

When configured with CA, a base station and/or a wireless device mayemploy an activation/deactivation mechanism of an SCell to improvebattery or power consumption of the wireless device. When a wirelessdevice is configured with one or more SCells, a gNB may activate ordeactivate at least one of the one or more SCells. Upon configuration ofan SCell, the SCell may be deactivated unless an SCell state associatedwith the SCell is set to “activated” or “dormant”.

A wireless device may activate/deactivate an SCell in response toreceiving an SCell Activation/Deactivation MAC CE. In an example, a gNBmay transmit, to a wireless device, one or more messages comprising anSCell timer (e.g., sCellDeactivationTimer). In an example, a wirelessdevice may deactivate an SCell in response to an expiry of the SCelltimer.

When a wireless device receives an SCell Activation/Deactivation MAC CEactivating an SCell, the wireless device may activate the SCell. Inresponse to the activating the SCell, the wireless device may performoperations comprising SRS transmissions on the SCell; CQI/PMI/RI/CRIreporting for the SCell; PDCCH monitoring on the SCell; PDCCH monitoringfor the SCell; and/or PUCCH transmissions on the SCell. In response tothe activating the SCell, the wireless device may start or restart afirst SCell timer (e.g., sCellDeactivationTimer) associated with theSCell. The wireless device may start or restart the first SCell timer inthe slot when the SCell Activation/Deactivation MAC CE activating theSCell has been received. In an example, in response to the activatingthe SCell, the wireless device may (re-)initialize one or more suspendedconfigured uplink grants of a configured grant Type 1 associated withthe SCell according to a stored configuration. In an example, inresponse to the activating the SCell, the wireless device may triggerPHR.

When a wireless device receives an SCell Activation/Deactivation MAC CEdeactivating an activated SCell, the wireless device may deactivate theactivated SCell. In an example, when a first SCell timer (e.g.,sCellDeactivationTimer) associated with an activated SCell expires, thewireless device may deactivate the activated SCell. In response to thedeactivating the activated SCell, the wireless device may stop the firstSCell timer associated with the activated SCell. In an example, inresponse to the deactivating the activated SCell, the wireless devicemay clear one or more configured downlink assignments and/or one or moreconfigured uplink grants of a configured uplink grant Type 2 associatedwith the activated SCell. In an example, in response to the deactivatingthe activated SCell, the wireless device may: suspend one or moreconfigured uplink grants of a configured uplink grant Type 1 associatedwith the activated SCell; and/or flush HARQ buffers associated with theactivated SCell.

When an SCell is deactivated, a wireless device may not performoperations comprising: transmitting SRS on the SCell; reportingCQI/PMI/RI/CRI for the SCell; transmitting on UL-SCH on the SCell;transmitting on RACH on the SCell; monitoring at least one first PDCCHon the SCell; monitoring at least one second PDCCH for the SCell; and/ortransmitting a PUCCH on the SCell. When at least one first PDCCH on anactivated SCell indicates an uplink grant or a downlink assignment, awireless device may restart a first SCell timer (e.g.,sCellDeactivationTimer) associated with the activated SCell. In anexample, when at least one second PDCCH on a serving cell (e.g. a PCellor an SCell configured with PUCCH, i.e. PUCCH SCell) scheduling theactivated SCell indicates an uplink grant or a downlink assignment forthe activated SCell, a wireless device may restart the first SCell timer(e.g., sCellDeactivationTimer) associated with the activated SCell. Inan example, when an SCell is deactivated, if there is an ongoing randomaccess procedure on the SCell, a wireless device may abort the ongoingrandom access procedure on the SCell.

FIG. 21A shows an example of an SCell Activation/Deactivation MAC CE ofone octet. A first MAC PDU subheader with a first LCID (e.g., ‘111010’as shown in FIG. 19 ) may identify the SCell Activation/Deactivation MACCE of one octet. The SCell Activation/Deactivation MAC CE of one octetmay have a fixed size. The SCell Activation/Deactivation MAC CE of oneoctet may comprise a single octet. The single octet may comprise a firstnumber of C-fields (e.g. seven) and a second number of R-fields (e.g.,one). FIG. 21B shows an example of an SCell Activation/Deactivation MACCE of four octets. A second MAC PDU subheader with a second LCID (e.g.,‘111001’ as shown in FIG. 19 ) may identify the SCellActivation/Deactivation MAC CE of four octets. The SCellActivation/Deactivation MAC CE of four octets may have a fixed size. TheSCell Activation/Deactivation MAC CE of four octets may comprise fouroctets. The four octets may comprise a third number of C-fields (e.g.,31) and a fourth number of R-fields (e.g., 1).

In FIG. 21A and/or FIG. 21B, a C_(i) field may indicate anactivation/deactivation status of an SCell with an SCell index i if anSCell with SCell index i is configured. In an example, when the C_(i)field is set to one, an SCell with an SCell index i may be activated. Inan example, when the C_(i) field is set to zero, an SCell with an SCellindex i may be deactivated. In an example, if there is no SCellconfigured with SCell index i, the wireless device may ignore the C_(i)field. In FIG. 21A and FIG. 21B, an R field may indicate a reserved bit.The R field may be set to zero.

A base station (gNB) may configure a wireless device (UE) with uplink(UL) bandwidth parts (BWPs) and downlink (DL) BWPs to enable bandwidthadaptation (BA) on a PCell. If carrier aggregation is configured, thegNB may further configure the UE with at least DL BWP(s) (i.e., theremay be no UL BWPs in the UL) to enable BA on an SCell. For the PCell, aninitial active BWP may be a first BWP used for initial access. For theSCell, a first active BWP may be a second BWP configured for the UE tooperate on the SCell upon the SCell being activated. In paired spectrum(e.g. FDD), a gNB and/or a UE may independently switch a DL BWP and anUL BWP. In unpaired spectrum (e.g. TDD), a gNB and/or a UE maysimultaneously switch a DL BWP and an UL BWP.

In an example, a gNB and/or a UE may switch a BWP between configuredBWPs by means of a DCI or a BWP inactivity timer. When the BWPinactivity timer is configured for a serving cell, the gNB and/or the UEmay switch an active BWP to a default BWP in response to an expiry ofthe BWP inactivity timer associated with the serving cell. The defaultBWP may be configured by the network. In an example, for FDD systems,when configured with BA, one UL BWP for each uplink carrier and one DLBWP may be active at a time in an active serving cell. In an example,for TDD systems, one DL/UL BWP pair may be active at a time in an activeserving cell. Operating on the one UL BWP and the one DL BWP (or the oneDL/UL pair) may improve UE battery consumption. BWPs other than the oneactive UL BWP and the one active DL BWP that the UE may work on may bedeactivated. On deactivated BWPs, the UE may: not monitor PDCCH; and/ornot transmit on PUCCH, PRACH, and UL-SCH.

In an example, a serving cell may be configured with at most a firstnumber (e.g., four) of BWPs. In an example, for an activated servingcell, there may be one active BWP at any point in time. In an example, aBWP switching for a serving cell may be used to activate an inactive BWPand deactivate an active BWP at a time. In an example, the BWP switchingmay be controlled by a PDCCH indicating a downlink assignment or anuplink grant. In an example, the BWP switching may be controlled by aBWP inactivity timer (e.g., bwp-InactivityTimer). In an example, the BWPswitching may be controlled by a MAC entity in response to initiating aRandom Access procedure. Upon addition of an SpCell or activation of anSCell, one BWP may be initially active without receiving a PDCCHindicating a downlink assignment or an uplink grant. The active BWP fora serving cell may be indicated by RRC and/or PDCCH. In an example, forunpaired spectrum, a DL BWP may be paired with a UL BWP, and BWPswitching may be common for both UL and DL.

FIG. 22 shows an example of BWP switching on an SCell. In an example, aUE may receive RRC message comprising parameters of a SCell and one ormore BWP configuration associated with the SCell. The RRC message maycomprise: RRC connection reconfiguration message (e.g.,RRCReconfiguration); RRC connection reestablishment message (e.g.,RRCRestablishment); and/or RRC connection setup message (e.g.,RRCSetup). Among the one or more BWPs, at least one BWP may beconfigured as the first active BWP (e.g., BWP 1), one BWP as the defaultBWP (e.g., BWP 0). The UE may receive a MAC CE to activate the SCell atn^(th) slot. The UE may start a SCell deactivation timer (e.g.,sCellDeactivationTimer), and start CSI related actions for the SCell,and/or start CSI related actions for the first active BWP of the SCell.The UE may start monitoring a PDCCH on BWP 1 in response to activatingthe SCell.

In an example, the UE may start restart a BWP inactivity timer (e.g.,bwp-InactivityTimer) at m-th slot in response to receiving a DCIindicating DL assignment on BWP 1. The UE may switch back to the defaultBWP (e.g., BWP 0) as an active BWP when the BWP inactivity timerexpires, at s-th slot. The UE may deactivate the SCell and/or stop theBWP inactivity timer when the sCellDeactivationTimer expires.

In an example, a MAC entity may apply normal operations on an active BWPfor an activated serving cell configured with a BWP comprising:transmitting on UL-SCH; transmitting on RACH; monitoring a PDCCH;transmitting PUCCH; receiving DL-SCH; and/or (re-) initializing anysuspended configured uplink grants of configured grant Type 1 accordingto a stored configuration, if any.

In an example, on an inactive BWP for each activated serving cellconfigured with a BWP, a MAC entity may: not transmit on UL-SCH; nottransmit on RACH; not monitor a PDCCH; not transmit PUCCH; not transmitSRS, not receive DL-SCH; clear any configured downlink assignment andconfigured uplink grant of configured grant Type 2; and/or suspend anyconfigured uplink grant of configured Type 1.

In an example, if a MAC entity receives a PDCCH for a BWP switching of aserving cell while a Random Access procedure associated with thisserving cell is not ongoing, a UE may perform the BWP switching to a BWPindicated by the PDCCH. In an example, if a bandwidth part indicatorfield is configured in DCI format 1_1, the bandwidth part indicatorfield value may indicate the active DL BWP, from the configured DL BWPset, for DL receptions. In an example, if a bandwidth part indicatorfield is configured in DCI format 0_1, the bandwidth part indicatorfield value may indicate the active UL BWP, from the configured UL BWPset, for UL transmissions.

In an example, for a primary cell, a UE may be provided by a higherlayer parameter Default-DL-BWP a default DL BWP among the configured DLBWPs. If a UE is not provided a default DL BWP by the higher layerparameter Default-DL-BWP, the default DL BWP is the initial active DLBipin an example, a UE may be provided by higher layer parameterbwp-InactivnyTimer, a timer value for the primary cell. If configured,the UE may increment the timer, if running, every interval of 1millisecond for frequency range 1 or every 0.5 milliseconds forfrequency range 2 if the UE may not detect a DCI format 1_1 for pairedspectrum operation or if the UE may not detect a DCI format 1_1 or DCIformat 0_1 for unpaired spectrum operation during the interval.

In an example, if a UE is configured for a secondary cell with higherlayer parameter Default-DL-BWP indicating a default DL BWP among theconfigured DL BWPs and the UE is configured with higher layer parameterbwp-InactivnyTimer indicating a timer value, the UE procedures on thesecondary cell may be same as on the primary cell using the timer valuefor the secondary cell and the default DL BWP for the secondary cell.

In an example, if a UE is configured by higher layer parameterActive-BWP-DL-SCell a first active DL BWP and by higher layer parameterActive-BWP-UL-SCell a first active UL BWP on a secondary cell orcarrier, the UE may use the indicated DL BWP and the indicated UL BWP onthe secondary cell as the respective first active DL BWP and firstactive UL BWP on the secondary cell or carrier.

In an example, a set of PDCCH candidates for a wireless device tomonitor is defined in terms of PDCCH search space sets. A search spaceset comprises a CSS set or a USS set. A wireless device monitors PDCCHcandidates in one or more of the following search spaces sets: aType0-PDCCH CSS set configured by pdcch-ConfigSIB1 in MIB or bysearchSpaceSIB1 in PDCCH-ConfigCommon or by searchSpaceZero inPDCCH-ConfigCommon for a DCI format with CRC scrambled by a SI-RNTI onthe primary cell of the MCG, a Type0A-PDCCH CSS set configured bysearchSpaceOtherSystemInformation in PDCCH-ConfigCommon for a DCI formatwith CRC scrambled by a SI-RNTI on the primary cell of the MCG, aType1-PDCCH CSS set configured by ra-SearchSpace in PDCCH-ConfigCommonfor a DCI format with CRC scrambled by a RA-RNTI or a TC-RNTI on theprimary cell, a Type2-PDCCH CSS set configured by pagingSearchSpace inPDCCH-ConfigCommon for a DCI format with CRC scrambled by a P-RNTI onthe primary cell of the MCG, a Type3-PDCCH CSS set configured bySearchSpace in PDCCH-Config with searchSpaceType=common for DCI formatswith CRC scrambled by INT-RNTI, SFI-RNTI, TPC-PUSCH-RNTI,TPC-PUCCH-RNTI, or TPC-SRS-RNTI and, only for the primary cell, C-RNTI,MCS-C-RNTI, or CS-RNTI(s), and a USS set configured by SearchSpace inPDCCH-Config with searchSpaceType=ue-Specific for DCI formats with CRCscrambled by C-RNTI, MCS-C-RNTI, SP-CSI-RNTI, or CS-RNTI(s).

In an example, a wireless device determines a PDCCH monitoring occasionon an active DL BWP based on one or more PDCCH configuration parameterscomprising: a PDCCH monitoring periodicity, a PDCCH monitoring offset,and a PDCCH monitoring pattern within a slot. For a search space set (SSs), the wireless device determines that a PDCCH monitoring occasion(s)exists in a slot with number n_(s,f) ^(μ) in a frame with number n_(f)if (n_(f)·N_(slot) ^(frame,μ)+n_(s,f) ^(μ)−o_(s)) mod k_(s)=0. N_(slot)^(frame,μ) is a number of slot in a frame when numerology μ isconfigured. o_(s) is a slot offset indicated in the PDCCH configurationparameters. k_(s) is a PDCCH monitoring periodicity indicated in thePDCCH configuration parameters. The wireless device monitors PDCCHcandidates for the search space set for T_(s) consecutive slots,starting from slot n_(s,f) ^(μ), and does not monitor PDCCH candidatesfor search space set s for the next k_(s)−T_(s) consecutive slots. In anexample, a USS at CCE aggregation level L∈{1, 2, 4, 8, 16} is defined bya set of PDCCH candidates for CCE aggregation level L. If a wirelessdevice is configured with CrossCarrierSchedulingConfig for a servingcell, the carrier indicator field value corresponds to the valueindicated by CrossCarrierSchedulingConfig.

In an example, a wireless device decides, for a search space set sassociated with CORESET p, CCE indexes for aggregation level Lcorresponding to PDCCH candidate m_(s,n) _(CI) of the search space setin slot n_(s,f) ^(μ) for an active DL BWP of a serving cellcorresponding to carrier indicator field value n_(CI) as

${{L \cdot \left\{ {\left( {Y_{p,n_{s,f}^{\mu}} + \left\lfloor \frac{m_{s,n_{CI}} \cdot N_{{CCE},p}}{L \cdot M_{s,\max}^{(L)}} \right\rfloor + n_{CI}} \right){mod}\left\lfloor {N_{{CCE},p}/L} \right\rfloor} \right\}} + i},$where, Y_(p,n) _(s,f) _(μ) =0 for any CSS; Y_(p,n) _(s,f) _(μ)=(A_(p)·Y_(p,n) _(s,f) _(μ) ⁻¹) mod D for a USS, Y_(p,-1)=n_(RNTI)≠0,A_(p)=39827 for p mod 3=0, A_(p)=39829 for p mod 3=1, A_(p)=39839 for pmod 3=2, and D=65537; i=0, . . . , L−1; N_(CCE,p) is the number of CCEs,numbered from 0 to N_(CCE,p)−1, in CORESET p; n_(CI) is the carrierindicator field value if the wireless device is configured with acarrier indicator field by CrossCarrierSchedulingConfig for the servingcell on which PDCCH is monitored; otherwise, including for any CSS,n_(CI)=0; m_(s,n) _(CI) =0, . . . , M_(s,n) _(CI) ^((L))−1, whereM_(s,n) _(CI) ^((L)) is the number of PDCCH candidates the wirelessdevice is configured to monitor for aggregation level L of a searchspace set s for a serving cell corresponding to n_(CI); for any CSS,M_(s,max) ^((L))=M_(s,0) ^((L)); for a USS, M_(s,max) ^((L)) is themaximum of M_(s,n) _(CI) ^((L)) over all configured n_(CI) values for aCCE aggregation level L of search space set s; and the RNTI value usedfor n_(RNTI) is the C-RNTI.

In an example, a UE may monitor a set of PDCCH candidates according toconfiguration parameters of a search space set comprising a plurality ofsearch spaces (SSs). The UE may monitor a set of PDCCH candidates in oneor more CORESETs for detecting one or more DCIs. Monitoring may comprisedecoding one or more PDCCH candidates of the set of the PDCCH candidatesaccording to the monitored DCI formats. Monitoring may comprise decodinga DCI content of one or more PDCCH candidates with possible (orconfigured) PDCCH locations, possible (or configured) PDCCH formats(e.g., number of CCEs, number of PDCCH candidates in common SSs, and/ornumber of PDCCH candidates in the UE-specific SSs) and possible (orconfigured) DCI formats. The decoding may be referred to as blinddecoding.

FIG. 23 shows an example of configuration of a SS. In an example, one ormore SS configuration parameters of a SS may comprise at least one of: aSS ID (searchSpaceId), a control resource set ID (controlResourceSetId),a monitoring slot periodicity and offset parameter(monitoringSlotPeriodicityAndOffset), a SS time duration value(duration), a monitoring symbol indication(monitoringSymbolsWithinSlot), a number of candidates for an aggregationlevel (nrofCandidates), and/or a SS type indicating a common SS type ora UE-specific SS type (searchSpaceType). The monitoring slot periodicityand offset parameter may indicate slots (e.g. in a radio frame) and slotoffset (e.g., related to a starting of a radio frame) for PDCCHmonitoring. The monitoring symbol indication may indicate on whichsymbol(s) of a slot a wireless device may monitor PDCCH on the SS. Thecontrol resource set ID may identify a control resource set on which aSS may be located.

FIG. 24 shows an example of configuration of a control resource set(CORESET). In an example, a base station may transmit to a wirelessdevice one or more configuration parameters of a CORESET. Theconfiguration parameters may comprise at least one of: a CORESET IDidentifying the CORESET, a frequency resource indication, a timeduration parameter indicating a number of symbols of the CORESET, aCCE-REG mapping type indicator, a plurality of TCI states, an indicatorindicating whether a TCI is present in a DCI, and the like. Thefrequency resource indication, comprising a number of bits (e.g., 45bits), indicates frequency domain resources, each bit of the indicationcorresponding to a group of 6 RBs, with grouping starting from the firstRB group in a BWP of a cell (e.g., SpCell, SCell). The first(left-most/most significant) bit corresponds to the first RB group inthe BWP, and so on. A bit that is set to 1 indicates that an RB group,corresponding to the bit, belongs to the frequency domain resource ofthis CORESET. Bits corresponding to a group of RBs not fully containedin the BWP within which the CORESET is configured are set to zero.

FIG. 25A shows an example of flow chart of data reception at a wirelessdevice. In an example, a wireless device receives one or more RRCmessages comprising configuration parameters of a cell, the cellcomprising one or more BWPs. The configuration parameters indicate oneor more CORESETs and/or one or more search spaces (SSs) configured on aBWP of the one or more BWPs. The one or more CORESETs and/or the one ormore SSs may be implemented as examples of FIG. 23 and/or FIG. 24 .

As shown in FIG. 25A, the wireless device, based on the one or more RRCmessages, may monitor PDCCH candidate(s) on a SS of the one or more SSsof a CORESET of the one or more CORESETs of an active BWP, for detectinga DCI indicating a downlink assignment over a PDSCH. Monitoring PDCCHcandidate(s) on a SS may comprises attempting to decode a DCI content ofthe PDCCH candidates with one or more PDCCH monitoring locations, one ormore CCEs based on aggregation levels, a number of PDCCH candidates, andone or more DCI formats. The one or more RRC messages may indicate thenumber of PDCCH candidates for each aggregation level on a SS. Thewireless device may determine a number of CCEs for each aggregationlevel for detecting a DCI. In an example, the wireless device maydetermine 1 CCE for detecting DCI when aggregation level is 1, 2 CCEswhen aggregation level is 2, 4 CCEs when aggregation level is 4, 8 CCEswhen aggregation level is 8, and 16 CCEs when aggregation level is 16.FIG. 25B shows an example of CCEs and REGs on a BWP.

In an example, a wireless device determines that a PDCCH monitoringoccasion(s) for an SS exist in a slot with number n_(s,f) ^(μ) in aframe with number n_(f) if (n_(f)·N_(slot) ^(frame,μ)+n_(s,f)^(μ)−o_(s))mod k_(s)=0. N_(slot) ^(frame,μ) is a number of slot in aframe when numerology μ is configured. o_(s) is a slot offset indicatedin configuration parameters of the SS. k_(s) is a PDCCH monitoringperiodicity indicated in the configuration parameters of the SS. Thewireless device monitors PDCCH candidates for the SS for T_(s)consecutive slots, starting from slot n_(s,f) ^(μ). The wireless devicemay not monitor PDCCH candidates for the SS for the next k_(s)−T_(s)consecutive slots. In an example, a USS at CCE aggregation level L∈{1,2, 4, 8, 16} is defined by a set of PDCCH candidates for CCE aggregationlevel L.

As shown in FIG. 25A, when monitoring PDCCH candidate(s) on a SS, thewireless device may receive (or decode successfully) a DCI, on one ormore CCEs. The one or more CCEs may start from a starting CCE index. TheDCI may comprise a time resource indicator for a downlink assignment, afrequency resource indicator for the downlink assignment, a PUCCHresource indicator (PRI), a PDSCH-to-HARQ_feedback timing indicator.

In response to receiving the DCI, the wireless device may receivesymbols of a transport block (TB) via the downlink assignment. Thewireless device may attempt to decode the TB based on the receivedsymbols. The wireless device may generate a positive acknowledgement(ACK) in response to the decoding being successful. The wireless devicemay generate a negative acknowledgement (NACK) in response to thedecoding not being successful.

In an example, the wireless device may transmit the ACK/NACK via a PUCCHresource at a time determined based on a value of thePDSCH-to-HARQ_feedback timing indicator. The wireless device maydetermine the PUCCH resource based on the PRI of the DCI, the startingCCE index of the one or more CCEs on which the wireless device receivesthe DCI, a cell index of a cell for which the wireless device monitorsthe PDCCH candidates, a RNTI value for receiving the DCI.

FIG. 25B shows an example of PUCCH resource determination. In anexample, a wireless device may receive one or more RRC messagescomprising configuration parameters of a BWP of a cell, the BWP, with abandwidth, comprising one or more radio resource unites (e.g., RBs asshown in FIG. 8 ). The configuration parameters may indicate resourceallocation of one or more CORESETs. A CORESET may consist of N_(RB)^(CORESET) (e.g., indicated by a RRC message as shown in FIG. 24 )resource blocks in the frequency domain and N_(symb) ^(CORESET)∈{1, 2,3} (e.g., indicated by an RRC message as shown in FIG. 24 ) symbols inthe time domain. The wireless device may determine N_(RB) ^(CORESET)based on high layer parameter (e.g., frequencyDomainResources) of theCORESET. As shown in FIG. 25B, the parameter frequencyDomainResourcesmay comprise a bitmap of frequency location indication, the bitmapcomprising one or more bits (e.g., 45 bits). Each bit of the bitmapcorresponds a group of 6 RBs (e.g., an RBG as shown in FIG. 25B), withgrouping starting from the first RB group in the BWP. The first(left-most/most significant) bit of the bitmap corresponds to the firstRB group in the BWP, and so on. A bit that is set to 1 indicates that anRB group, corresponding to the bit, belongs to the frequency domainresource of the CORESET. A bit that is set to 0 indicates that an RBgroup, corresponding to the bit, does not belong to the frequency domainresource of the CORESET.

In an example, the wireless device may monitor a PDCCH candidate of aSS, on one or more CCEs with the RBGs of the CORESET on an active BWP. ACCE may consist of a number (e.g., 6) of resource-element groups (REGs).A REG may comprise one RB during one OFDM symbol. REGs within a CORESETare numbered in increasing order in a time-first manner, starting with 0for the first OFDM symbol and the lowest-numbered resource block in theCORESET. In an example, a CORESET is configured with one CCE-to-REGmapping indicator.

In an example, CCE-to-REG mapping for a CORESET may be interleaved ornon-interleaved and is described by REG bundles:

-   -   REG bundle i is defined as REGs {iL, iL+1, . . . , iL+L−1} where        L is the REG bundle size, i=0, 1, . . . , N_(REG)        ^(CORESET)/L−1, and N_(REG) ^(CORESET)=N_(RB) ^(CORESET)N_(symb)        ^(CORESET) is the number of REGs in the CORESET;    -   CCE j consists of REG bundles {f(6j/L), f(6j/L+1), . . . ,        f(6j/L+6/L−1)} where f(⋅) is an interleaver.

In an example, for non-interleaved CCE-to-REG mapping, L=6 and f(x)=x.In an example, for interleaved CCE-to-REG mapping, L∈{2,6} for N_(symb)^(CORESET)=1 and L∈{N_(symb) ^(CORESET), 6} for N_(symb) ^(CORESET)∈{2,3}. The interleaver is defined by:f(x)=(rC+c+n _(shift))mod(N _(REG) ^(CORESET) /L)x=cR+rr=0,1, . . . ,R−1c=0,1, . . . ,C−1C=N _(REG) ^(CORESET)/(LR)where R∈{2, 3, 6}.

In an example, a set of PDCCH candidates for a UE to monitor is definedin terms of PDCCH search space sets. A search space set may be a CSS setor a USS set. A UE monitors PDCCH candidates in one or more of thefollowing search spaces sets

-   -   a Type0-PDCCH CSS set configured by pdcch-ConfigSIB1 in MIB or        by searchSpaceSIB1 in PDCCH-ConfigCommon or by searchSpaceZero        in PDCCH-ConfigCommon for a DCI format with CRC scrambled by a        SI-RNTI on the primary cell of the MCG;    -   a Type0A-PDCCH CSS set configured by        searchSpaceOtherSystemInformation in PDCCH-ConfigCommon for a        DCI format with CRC scrambled by a SI-RNTI on the primary cell        of the MCG;    -   a Type1-PDCCH CSS set configured by ra-SearchSpace in        PDCCH-ConfigCommon for a DCI format with CRC scrambled by a        RA-RNTI or a TC-RNTI on the primary cell;    -   a Type2-PDCCH CSS set configured by pagingSearchSpace in        PDCCH-ConfigCommon for a DCI format with CRC scrambled by a        P-RNTI on the primary cell of the MCG;    -   a Type3-PDCCH CSS set configured by SearchSpace in PDCCH-Config        with searchSpaceType=common for DCI formats with CRC scrambled        by INT-RNTI, SFI-RNTI, TPC-PUSCH-RNTI, TPC-PUCCH-RNTI, or        TPC-SRS-RNTI and, only for the primary cell, C-RNTI, MCS-C-RNTI,        or CS-RNTI(s), and    -   a USS set configured by SearchSpace in PDCCH-Config with        searchSpaceType=ue-Specific for DCI formats with CRC scrambled        by C-RNTI, MCS-C-RNTI, SP-CSI-RNTI, or CS-RNTI(s).

In an example, a wireless device decides, for a search space set sassociated with CORESET p, CCE indexes for aggregation level Lcorresponding to PDCCH candidate m_(s,n) _(CI) of the search space setin slot n_(s,f) ^(μ) for an active DL BWP of a serving cellcorresponding to carrier indicator field value n_(CI) as

${{L \cdot \left\{ {\left( {Y_{p,n_{s,f}^{\mu}} + \left\lfloor \frac{m_{s,n_{CI}} \cdot N_{{CCE},p}}{L \cdot M_{s,\max}^{(L)}} \right\rfloor + n_{CI}} \right){mod}\left\lfloor {N_{{CCE},p}/L} \right\rfloor} \right\}} + i},$where, Y_(p,n) _(s,f) _(μ) =0 for any CSS; Y_(p,n) _(s,f) _(μ)=(A_(p)·Y_(p,n) _(s,f) _(μ) ⁻¹) mod D for a USS, Y_(p,-1)=n_(RNTI)≠0,A_(p)=39827 for p mod 3=0, A_(p)=39829 for p mod 3=1, A_(p)=39839 for pmod 3=2, and D=65537; i=0, . . . , L−1; N_(CCE,p) is the number of CCEs,numbered from 0 to N_(CCE,p)−1, in CORESET p; n_(CI) is the carrierindicator field value if the wireless device is configured with acarrier indicator field by CrossCarrierSchedulingConfig for the servingcell on which PDCCH is monitored; otherwise, including for any CSS,n_(CI)=0; m_(s,n) _(CI) =0, . . . , M_(s,n) _(CI) ^((L))−1, whereM_(s,n) _(CI) ^((L)) is the number of PDCCH candidates the wirelessdevice is configured to monitor for aggregation level L of a searchspace set s for a serving cell corresponding to n_(CI); for any CSS,M_(s,max) ^((L))=M_(s,0) ^((L)); for a USS, M_(s,max) ^((L)) is themaximum of M_(s,n) _(CI) ^((L)) over all configured n_(CI) values for aCCE aggregation level L of search space set s; and the RNTI value usedfor n_(RNTI) is the C-RNTI.

As shown in FIG. 25B, a BWP of a cell may comprise M RBGs, indexing fromRBG 0 to RBG M−1. A CORESET configured on the BWP may occupy a number ofRBGs of the M RBGs, based on a bitmap (e.g., frequencyDomainResources).Bit 0, corresponding to RBG 0, being set to 1, may indicate RBG 0 belongto the CORESET, and so on. Radio resources of the number of RBGs may mapto a number of CCEs, the number of CCEs indexed from CCE 0 to CCE N−1,based on CCE-to-REG mapping indicator (e.g., cce-REG-MappingType). Thewireless device may monitor PDCCH candidates of a SS on a subset of thenumber of CCEs, e.g., comprising CCE 2, CCE 4, CCE 6, and so on.

In an example, the wireless device may receive a DCI on the SS, startingfrom CCE 2, based on the equation above. The wireless device maydetermine, for HARQ-ACK feedback, a PUCCH resource based on a PRI valueof the DCI, a starting CCE index (e.g., CCE 2 in the example of FIG.25B).

In an example, a wireless device may not have dedicated PUCCH resourceconfiguration. The wireless device may determine a PUCCH resource setbased on a predefined PUCCH resource table, for transmission of HARQ-ACKinformation on PUCCH. The PUCCH resource set includes sixteen resources,each corresponding to a PUCCH format, a starting symbol, a duration, aPRB offset, and a cyclic shift index set for a PUCCH transmission.

In an example, the wireless device may determine a PUCCH resource withindex

$r_{PUCCH},{0 \leq r_{PUCCH} \leq 15},{{{as}r_{PUCCH}} = {\left\lfloor \frac{2 \cdot n_{{CCE},0}}{N_{CCE}} \right\rfloor + {2 \cdot \Delta_{PRI}}}},$where N_(CCE) is a number of CCEs (e.g., K in the example of FIG. 25B)in a CORESET of a PDCCH reception with the DCI, n_(CCE,0) is the indexof a first CCE (e.g., 2 in the example of FIG. 25B) for the PDCCHreception, and Δ_(PRI) is a value of the PRI field in the DCI. In theexample of FIG. 25B, r_(PUCCH)=2.

In an example, a wireless device may be configured with dedicated PUCCHresource configuration by higher layers. In an example, a PUCCH resourcemay comprise: a PUCCH resource index (e.g., provided bypucch-ResourceId), an index of the first PRB prior to frequency hoppingor for no frequency hopping by startingPRB, an index of the first PRBafter frequency hopping by secondHopPRB, an indication for intra-slotfrequency hopping by intraSlotFrequencyHopping, and/or a configurationfor a PUCCH format, from PUCCH format 0 through PUCCH format 4, providedby format.

In an example, when a wireless device transmits HARQ-ACK information ina PUCCH in response to detecting a last DCI (e.g., DCI format 1_0 or DCIformat 1_1) in a PDCCH reception, among multiple DCIs with a value ofthe PDSCH-to-HARQ_feedback timing indicator field indicating a same slotfor the PUCCH transmission, the wireless device determines a PUCCHresource, from a set of PUCCH resources (e.g., the first set whenconfigured with multiple sets of PUCCH resources), with index r_(PUCCH),0≤r_(PUCCH)≤R_(PUCCH)−1, as

$r_{PUCCH} = \begin{Bmatrix}{\left\lfloor \frac{n_{{CCE},p} \cdot \left\lceil {R_{PUCCH}/8} \right\rceil}{N_{{CCE},p}} \right\rfloor + {\Delta_{PRI} \cdot \left\lceil \frac{R_{PUCCH}}{8} \right\rceil}} & {{{if}{}\Delta_{PRI}} < {R_{PUCCH}{mod}8}} \\{\left\lfloor \frac{n_{{CCE},p} \cdot \left\lfloor {R_{PUCCH}/8} \right\rfloor}{N_{{CCE},p}} \right\rfloor + {\Delta_{PRI} \cdot \left\lfloor \frac{R_{PUCCH}}{8} \right\rfloor} + {R_{PUCCH}{mod}8}} & {{{if}\Delta_{PRI}} \geq {R_{PUCCH}{mod}8}}\end{Bmatrix}$when the size R_(PUCCH) of resourceList of the first set of PUCCHresources is larger than eight. In an example, N_(CCE,p) is a number ofCCEs (e.g., K in the example of FIG. 25B) in CORESET p of the PDCCHreception for the DCI. n_(CCE,p) is the index of a first CCE (e.g., 2 inthe example of FIG. 25B) for the PDCCH reception, and Δ_(PRI) is a valueof the PRI field in the DCI.

In an example, a wireless device may transmit one or more uplink controlinformation (UCI) via one or more PUCCH resources to a base station. Theone or more UCI may comprise at least one of: HARQ-ACK information;scheduling request (SR); and/or CSI report. In an example, a PUCCHresource may be identified by at least: frequency location (e.g.,starting PRB); and/or a PUCCH format. The PUCCH format may be configuredwith an initial cyclic shift value of a base sequence and a time domainlocation parameter (e.g., starting symbol index). In an example, a PUCCHformat may comprise at least one of PUCCH format 0, PUCCH format 1,PUCCH format 2, PUCCH format 3, or PUCCH format 4. A PUCCH format 0 mayhave a length of 1 or 2 OFDM symbols and be less than or equal to 2bits. A PUCCH format 1 may occupy a number between 4 and 14 of OFDMsymbols and be less than or equal to 2 bits. A PUCCH format 2 may occupy1 or 2 OFDM symbols and be greater than 2 bits. A PUCCH format 3 mayoccupy a number between 4 and 14 of OFDM symbols and be greater than 2bits. A PUCCH format 4 may occupy a number between 4 and 14 of OFDMsymbols and be greater than 2 bits. The PUCCH resource may be configuredon a PCell, or a PUCCH secondary cell.

In an example, when configured with multiple UL BWPs, a base station maytransmit to a wireless device, one or more RRC messages comprisingconfiguration parameters of one or more PUCCH resource sets (e.g., 1, 2,3, 4, or greater than 4) on an UL BWP of the multiple UL BWPs. EachPUCCH resource set may be configured with a PUCCH resource set index, alist of PUCCH resources with each PUCCH resource being identified by aPUCCH resource identifier (e.g., pucch-Resourceid), and/or a maximumnumber of UCI information bits a wireless device may transmit using oneof the list of PUCCH resources in the PUCCH resource set.

In an example, when configured with one or more PUCCH resource sets, awireless device may select one of the one or more PUCCH resource setsbased on a bit length of UCI information bits (e.g., HARQ-ARQ bits, SR,and/or CSI) the wireless device will transmit. In an example, when thebit length of UCI information bits is less than or equal to 2, thewireless device may select a first PUCCH resource set with the PUCCHresource set index equal to “0”. In an example, when the bit length ofUCI information bits is greater than 2 and less than or equal to a firstconfigured value, the wireless device may select a second PUCCH resourceset with the PUCCH resource set index equal to “1”. In an example, whenthe bit length of UCI information bits is greater than the firstconfigured value and less than or equal to a second configured value,the wireless device may select a third PUCCH resource set with the PUCCHresource set index equal to “2”. In an example, when the bit length ofUCI information bits is greater than the second configured value andless than or equal to a third value (e.g., 1706), the wireless devicemay select a fourth PUCCH resource set with the PUCCH resource set indexequal to “3”.

In an example, a wireless device may determine, based on a number ofuplink symbols of UCI transmission and a number of UCI bits, a PUCCHformat from a plurality of PUCCH formats comprising PUCCH format 0,PUCCH format 1, PUCCH format 2, PUCCH format 3 and/or PUCCH format 4. Inan example, the wireless device may transmit UCI in a PUCCH using PUCCHformat 0 if the transmission is over 1 symbol or 2 symbols and thenumber of HARQ-ACK information bits with positive or negative SR(HARQ-ACK/SR bits) is 1 or 2. The PUCCH format 0 may be based onDFT-spread OFDM, e.g., to reduce cubic metric. In an example, thewireless device may transmit UCI in a PUCCH using PUCCH format 1 if thetransmission is over 4 or more symbols and the number of HARQ-ACK/SRbits is 1 or 2. The PUCCH format 1 may be based on DFT-spread OFDM,e.g., to reduce cubic metric. In an example, the wireless device maytransmit UCI in a PUCCH using PUCCH format 2 if the transmission is over1 symbol or 2 symbols and the number of UCI bits is more than 2. ThePUCCH format 2 may be based on OFDM. In an example, the wireless devicemay transmit UCI in a PUCCH using PUCCH format 3 if the transmission isover 4 or more symbols, the number of UCI bits is more than 2 and PUCCHresource does not include an orthogonal cover code. The PUCCH format 3may be based on DFT-spread OFDM, e.g., to reduce cubic metric. In anexample, the wireless device may transmit UCI in a PUCCH using PUCCHformat 4 if the transmission is over 4 or more symbols, the number ofUCI bits is more than 2 and the PUCCH resource includes an orthogonalcover code. The PUCCH format 4 may be based on DFT-spread OFDM, e.g., toreduce cubic metric.

In an example, in order to transmit HARQ-ACK information on a PUCCHresource, a wireless device may determine the PUCCH resource from aPUCCH resource set. The PUCCH resource set may be determined asmentioned above. The wireless device may determine the PUCCH resourcebased on a PUCCH resource indicator field in a DCI (e.g., with a DCIformat 1_0 or DCI for 1_1) received on a PDCCH. A 3-bit PUCCH resourceindicator field in the DCI may indicate one of eight PUCCH resources inthe PUCCH resource set. The wireless device may transmit the HARQ-ACKinformation in a PUCCH resource indicated by the 3-bit PUCCH resourceindicator field in the DCI.

FIG. 26 shows an example of mapping of PUCCH resource indication (PRI)field value to PUCCH resource in a PUCCH resource set (e.g., withmaximum 8 PUCCH resources). In an example, when the PUCCH resourceindicator in the DCI (e.g., DCI format 1_0 or 1_1) is ‘000’, thewireless device may determine a PUCCH resource identified by a PUCCHresource identifier (e.g., pucch-Resourdceid) with a first value in thePUCCH resource list of the PUCCH resource set. When the PUCCH resourceindicator in the DCI (e.g., DCI format 1_0 or 1_1) is ‘001’, thewireless device may determine a PUCCH resource identified by a PUCCHresource identifier (e.g., pucch-Resourdceid) with a second value in thePUCCH resource list of the PUCCH resource set, etc. Similarly, in orderto transmit HARQ-ACK information, SR and/or CSI multiplexed in a PUCCH,the wireless device may determine the PUCCH resource based on at leastthe PUCCH resource indicator in a DCI (e.g., DCI format 1_0/1_1), from alist of PUCCH resources in a PUCCH resource set.

In an example embodiment, Listen-before-talk (LBT) may be implementedfor transmission in a cell configured in unlicensed band (referred to asa LAA cell and/or a NR-U cell for the sake of convenience, for example,an LAA cell and NR-U cell may be interchangeable and may refer any celloperating in unlicensed band. The cell may be operated as non-standalonewith an anchor cell in a licensed band or standalone without an anchorcell in licensed band). The LBT may comprise a clear channel assessment.For example, in an LBT procedure, equipment may apply a clear channelassessment (CCA) check before using the channel. For example, the CCAcomprise at least energy detection that determines the presence (e.g.,channel is occupied) or absence (e.g., channel is clear) of othersignals on a channel. A regulation of a country may impact on the LBTprocedure. For example, European and Japanese regulations mandate theusage of LBT in the unlicensed bands, for example in 5 GHz unlicensedband. Apart from regulatory requirements, carrier sensing via LBT may beone way for fair sharing of the unlicensed spectrum.

In an example embodiment, discontinuous transmission on an unlicensedcarrier with limited maximum transmission duration may be enabled. Someof these functions may be supported by one or more signals to betransmitted from the beginning of a discontinuous downlink transmissionin the unlicensed band Channel reservation may be enabled by thetransmission of signals, by an NR-U node, after or in response togaining channel access based on a successful LBT operation. Other nodesmay receive the signals (e.g., transmitted for the channel reservation)with an energy level above a certain threshold that may sense thechannel to be occupied. Functions that may need to be supported by oneor more signals for operation in unlicensed band with discontinuousdownlink transmission may comprise one or more of the following:detection of the downlink transmission in unlicensed band (includingcell identification) by wireless devices; time and frequencysynchronization of a wireless devices.

In an example embodiment, DL transmission and frame structure design foran operation in unlicensed band may employ subframe, (mini-)slot, and/orsymbol boundary alignment according to carrier aggregation timingrelationships across serving cells aggregated by CA. This may not implythat the base station transmissions start at the subframe, (mini-)slot,and/or symbol boundary. Unlicensed cell operation (e.g., LAA and/orNR-U) may support transmitting PDSCH, for example, when not all OFDMsymbols are available for transmission in a subframe according to LBT.Delivery of necessary control information for the PDSCH may besupported.

An LBT procedure may be employed for fair and friendly coexistence of3GPP system (e.g., LTE and/or NR) with other operators and technologiesoperating in unlicensed spectrum. For example, a node attempting totransmit on a carrier in unlicensed spectrum may perform a clear channelassessment (e.g., as a part of one or more LBT procedures) to determineif the channel is free for use. An LBT procedure may involve at leastenergy detection to determine if the channel is being used. For example,regulatory requirements in some regions, e.g., in Europe, specify anenergy detection threshold such that if a node receives energy greaterthan this threshold, the node assumes that the channel is not free.While nodes may follow such regulatory requirements, a node mayoptionally use a lower threshold for energy detection than thatspecified by regulatory requirements. A radio access technology (e.g.,LTE and/or NR) may employ a mechanism to adaptively change the energydetection threshold. For example, NR-U may employ a mechanism toadaptively lower the energy detection threshold from an upper bound.Adaptation mechanism may not preclude static or semi-static setting ofthe threshold. In an example Category 4 LBT (CAT4 LBT) mechanism orother type of LBT mechanisms may be implemented.

Various example LBT mechanisms may be implemented. In an example, forsome signals, in some implementation scenarios, in some situations,and/or in some frequencies no LBT procedure may be performed by thetransmitting entity. In an example, Category 1 (CAT1, e.g., no LBT) maybe implemented in one or more cases. For example, a channel inunlicensed band may be hold by a first device (e.g., a base station forDL transmission), and a second device (e.g., a wireless device) takesover the for a transmission without performing the CAT1 LBT. In anexample, Category 2 (CAT2, e.g. LBT without random back-off and/orone-shot LBT) may be implemented. The duration of time determining thatthe channel is idle may be deterministic (e.g., by a regulation). A basestation may transmit an uplink grant indicating a type of LBT (e.g.,CAT2 LBT) to a wireless device. CAT1 LBT and CAT2 LBT may be employedfor COT sharing. For example, a base station may transmit an uplinkgrant (resp. uplink control information) comprising a type of LBT. Forexample, CAT1 LBT and/or CAT2 LBT in the uplink grant (or uplink controlinformation) may indicate, to a receiving device (e.g., a base station,and/or a wireless device) to trigger COT sharing. In an example,Category 3 (CAT3, e.g. LBT with random back-off with a contention windowof fixed size) may be implemented. The LBT procedure may have thefollowing procedure as one of its components. The transmitting entitymay draw a random number N within a contention window. The size of thecontention window may be specified by the minimum and maximum value ofN. The size of the contention window may be fixed. The random number Nmay be employed in the LBT procedure to determine the duration of timethat the channel is sensed to be idle before the transmitting entitytransmits on the channel. In an example, Category 4 (CAT4, e.g. LBT withrandom back-off with a contention window of variable size) may beimplemented. The transmitting entity may draw a random number N within acontention window. The size of contention window may be specified by theminimum and maximum value of N. The transmitting entity may vary thesize of the contention window when drawing the random number N. Therandom number N may be used in the LBT procedure to determine theduration of time that the channel is sensed to be idle before thetransmitting entity transmits on the channel.

In an unlicensed band, a type of LBT (CAT1, CAT2, CAT3, and/or CAT4) maybe configured via control messages (RRC, MAC CE, and/or DCI) per a cell.In an example, a type of LBT (CAT1, CAT2, CAT3, and/or CAT4) may beconfigured via control messages (RRC, MAC CE, and/or DCI) per BWP. Forexample, a type of LBT (CAT1, CAT2, CAT3, and/or CAT4) may be determinedat least based on a numerology configured in a BWP. In this case, BWPswitching may change a type of LBT.

In an example, a wireless device may employ uplink (UL) LBT. The UL LBTmay be different from a downlink (DL) LBT (e.g. by using different LBTmechanisms or parameters) for example, since the NR-U UL may be based onscheduled access which affects a wireless device's channel contentionopportunities. Other considerations motivating a different UL LBTcomprise, but are not limited to, multiplexing of multiple wirelessdevices in a subframe (slot, and/or mini-slot).

In an example, DL transmission burst(s) may be a continuous (unicast,multicast, broadcast, and/or combination thereof) transmission by a basestation (e.g., to one or more wireless devices) on a carrier component(CC). UL transmission burst(s) may be a continuous transmission from oneor more wireless devices to a base station on a CC. In an example, DLtransmission burst(s) and UL transmission burst(s) on a CC in anunlicensed spectrum may be scheduled in a TDM manner over the sameunlicensed carrier. Switching between DL transmission burst(s) and ULtransmission burst(s) may require an LBT (e.g., CAT1 LBT, CAT2 LBT, CAT3LBT, and/or CAT4 LBT). For example, an instant in time may be part of aDL transmission burst and/or an UL transmission burst.

Channel occupancy time (COT) sharing may be employed in a radio accesstechnology (e.g., LTE and or NR). COT sharing may be a mechanism thatone or more wireless devices share a channel that is sensed as idle byat least one of the one or more wireless devices. For example, one ormore first devices occupy a channel an LBT (e.g., the channel is sensedas idle based on CAT4 LBT) and one or more second devices shares itusing an LBT (e.g., 25 us LBT) within a maximum COT (MCOT) limit. Forexample, the MOCT limit may be given per priority class, logical channelpriority, and/or wireless device specific. COT sharing may allow aconcession for UL in unlicensed band. For example, a base station maytransmit an uplink grant to a wireless device for a UL transmission. Forexample, a base station may occupy a channel and transmit, to one ormore wireless devices, a control signal indicating that the one or morewireless devices may use the channel. For example, the control signalmay comprise an uplink grant and/or a particular LBT type (e.g., CAT1LBT and/or CAT2 LBT). The one or more wireless device may determine COTsharing based at least on the uplink grant and/or the particular LBTtype. The wireless device may perform UL transmission(s) with dynamicgrant and/or configured grant (e.g., Type 1, Type2, autonomous UL) witha particular LBT (e.g., CAT2 LBT such as 25 us LBT) in the configuredperiod, for example, if a COT sharing is triggered. A COT sharing may betriggered by a wireless device. For example, a wireless deviceperforming UL transmission(s) based on a configured grant (e.g., Type 1,Type2, autonomous UL) may transmit an uplink control informationindicating the COT sharing (UL-DL switching within a (M)COT). A startingtime of DL transmission(s) in the COT sharing triggered by a wirelessdevice may be indicated by one or more ways. For example, one or moreparameters in the uplink control information indicate the starting time.For example, resource configuration(s) of configured grant(s)configured/activated by a base station may indicate the starting time.For example, a base station may be allowed to perform DL transmission(s)after or in response to UL transmission(s) on the configured grant(e.g., Type 1, Type 2, and/or autonomous UL). There may be a delay(e.g., at least 4 ms) between the uplink grant and the UL transmission.The delay may be predefined, semi-statically configured (via a RRCmessage) by a base station, and/or dynamically indicated (e.g., via anuplink grant) by a base station. The delay may not be accounted in theCOT duration.

In an example, initial active DL/UL BWP may be 20 MHz (or approximately)for a first unlicensed band, e.g., in a 5 GHz unlicensed band. Aninitial active DL/UL BWP in one or more unlicensed bands may be similar(e.g., approximately 20 MHz in a 5 GHz and/or 6 GHz unlicensedspectrum), for example, if similar channelization is used in the one ormore unlicensed bands (e.g., by a regulation). For a wideband case, abase station may configure a wideband with one or more BWP. For example,for 80 MHz case, a base station may configure four BWPs; each BWP may beconfigured with about 20 MHz. An active BWP (DL and/or UL) may beswitched from one to another at least based on BWP switching mechanism.For example, a base station may configure the wideband with one or moresubbands when the cell comprises a single BWP. For example, for 80 MHzcase, a base station may configure four subbands; each subband may beconfigured with about 20 MHz. For example, a wireless device may performan LBT subband by subband, and may transmit data via scheduled resourceson one or more subbands where the LBT indicates idle.

In an example, carrier aggregation between PCell configured on alicensed band and SCell configured on unlicensed band may be supported.In an example, SCell may have both DL and UL, or DL-only. In an example,dual connectivity between PCell (e.g., LTE cell) configured on alicensed band and PSCell (e.g., NR-U cell) configured on unlicensed bandmay be supported. In an example, Stand-alone operation on an unlicensedband, where all carriers are in one or more unlicensed bands, may besupported. In an example, a cell with DL in unlicensed band and UL in alicensed band or vice versa may be supported. In an example, dualconnectivity between PCell (e.g., NR cell) on a licensed band and PSCell(e.g., NR-U cell) on unlicensed band may be supported.

In an example, a radio access technology (e.g., LTE and/or NR) operatingbandwidth may be an integer multiple of 20 MHz, for example, if absenceof Wi-Fi cannot be guaranteed (e.g. by regulation) in an unlicensed band(e.g., 5 GHz, 6 GHZ, and/or sub-7 GHz) where the radio access technology(e.g., LTE and/or NR) is operating. In an example, a wireless device mayperform one or more LBTs in units of 20 MHz. In an example, receiverassisted LBT (e.g., RTS/CTS type mechanism) and/or on-demand receiverassisted LBT (e.g., for example receiver assisted LBT enabled only whenneeded) may be employed. In an example, techniques to enhance spatialreuse may be used.

In an example, wideband carrier with more than one channels (e.g.,subbands, SBs, RB sets) is supported on in an unlicensed band. In anexample, there may be one active BWP in a carrier. A channel (a subband,RB set, etc.) may comprise a number of RBs within a BWP for data/controlsignal transmission. In this specification, a channel may be (equally)referred to as a subband, a SB, an RB set, etc. In an example, a BWPwith one or more channels may be activated. In an example, when absenceof Wi-Fi cannot be guaranteed (e.g. by regulation), LBT may be performedin units of 20 MHz. In this case, there may be multiple parallel LBTprocedures for this BWP. The actual transmission bandwidth may besubject to SB with LBT success, which may result in dynamic bandwidthtransmission within this active wideband BWP.

In an example, one or more active BWPs may be supported. To improve theBWP utilization efficiency, the BWP bandwidth may be the same as thebandwidth of SB for LBT, e.g., LBT may be carried out on each BWP. Thenetwork may activate/deactivate the BWPs based on data volume to betransmitted. In an example, one or more non-overlapped BWPs may beactivated for a wireless device within a wide component carrier, whichmay be similar as carrier aggregation. To improve the BWP utilizationefficiency, the BWP bandwidth may be the same as the bandwidth of SB forLBT, i.e. LBT may be a carrier out on each BWP. When LBT on more thanone SB is successful, it requires a wireless device to have thecapability to support one or more narrow RF or a wide RF which maycomprise the one or more activated BWPs.

In an example, a single wideband BWP may be activated for a wirelessdevice within a component carrier. The bandwidth of wideband BWP may bein the unit of SB for LBT. For example, if the SB for LBT is 20 MHz in 5GHz band, the wideband BWP bandwidth may comprise multiple 20 MHz. Theactual transmission bandwidth may be subject to SB with LBT success,which may result in dynamic bandwidth transmission within this activewideband BWP.

In an example, with wideband (e.g., 80 MHz) configuration on a BWP,frequency resources of a SS (or CORESET) may be spread (or across)within the BWP. Frequency resources of a SS (or CORESET) may be confinedwithin a SB of the BWP. A SB may be in unit of 20 MHz, e.g., for LBTprocedure in a NR-U cell. FIG. 27A and FIG. 27B show two SS/CORESETconfigurations in frequency domain in a BWP of a plurality of BWPs of acell, or in a cell (in case of a single BWP configured on the cell).

FIG. 27A shows an example of SS/CORESET configuration in a BWP. In anexample, a frequency resource indication of 1^(st) SS or 1^(st) CORESETconfiguration may indicate frequency resources spread on a number of RBgroups in the BWP, the number of RB groups not being confined or withina SB (e.g., 20 MHz) of the BWP. Spreading the frequency resources withinthe BWP may enable a base station to flexibly distribute PDCCH resourcesfor different UEs, or different signalling purpose (e.g., common, orUE-specific).

FIG. 27B show an example of SS/CORESET configuration in a BWP. In anexample, a frequency resource indication of 1^(st) SS or 1^(st) CORESETconfiguration may indicate frequency resources are confined in abandwidth (e.g., 20 MHz) of a first SB (SB 0 in FIG. 27B) of the BWP. Tomaintain UE's capability of CORESETs/SSs configuration (e.g., at most 40SS s per cell, or at most 12 or 20 CORESETs per cell) same (orsimilarly) as in case of operating in a licensed cell, a CORESET,identified by a CORESET ID, may be allocated with a same number of RBs(or RB groups) in each SB of the BWP. The same number of RBs (or RBgroups) may be located in the same frequency locations (e.g., relativeto a starting frequency location of each SB) of each SB of the BWP. Asshown above, the pattern of mapping the CORESET to RBs of a SB may bereplicated to the mapping of the CORESET to other SBs of the BWP.

In an example, a BWP may comprise a number (e.g., 4) of LBT SBs (SBs, orRB sets), each LBT SB occupying a number of RBs (or RB groups) of theBWP. A first LBT SB may overlap in frequency domain with a second LBTSB. A first LBT SB may not overlap in frequency domain with a second LBTSB.

In response to the frequency resource of 1^(st) CORESET being confinedin a bandwidth of a SB of the BWP and be replicated to each SB of theBWP, the wireless device may monitor PDCCH on the 1^(st) SS of the1^(st) CORESET on one or more SBs (e.g., SB 0, SB 1 in FIG. 27B) of thenumber of SBs of the BWP, based on configuration or predefined rules.Confining frequency resources of a CORESET within a bandwidth of a SB ofa BWP may increase signalling transmission robustness and/or save powerconsumption of the wireless device. In an example, a base station mayperform LBT procedure per SB of the BWP. In response to the LBTprocedure being successful on one of the SBs of the BWP, the basestation may transmit DCI via a PDCCH on the one of the SBs of the BWP.In response to the LBT procedure being successful on more than one ofthe SBs of the BWP, the base station may transmit DCI via a PDCCH on themore than one of the SBs of the BWP, or the base station may transmitmultiple DCI via PDCCH on the more than one of the SBs of the BWP, eachDCI transmitted on a corresponding one of the more than one of the SBs.

In an example, a base station may allocate for a CORESET (e.g., in highlayer parameter frequencyDomainResources of the CORESET in RRC messages,as shown in FIG. 24 ) physical resource blocks (PRBs) confined withinone of SBs of the BWP corresponding to the CORESET, for a search spaceset configuration associated with multiple monitoring locations infrequency domain. Within the search space set associated with theCORESET, each of the multiple monitoring locations in the frequencydomain corresponds to (and/or is confined within) a SB of the SBs. Eachof the multiple monitoring locations may have a frequency domainresource allocation pattern that is replicated from the patternconfigured in the CORESET. In an example, CORESET parameters other thanfrequency domain resource allocation pattern may be identical for eachof the multiple monitoring locations in the frequency domain.

In an example, a wireless device, before receiving a DCI, may not beaware of on which SB a base station may succeed an LBT procedure (e.g.,when the LBT procedure indicates channel is clear on a SB), and may notbe aware of on which SB the base station may transmit the DCI. Whenconfigured with multiple LBT SBs on a BWP, the wireless device maymonitor PDCCH on the multiple SBs for receiving the DCI.

In an example, a base station may transmit to a wireless device one ormore RRC messages comprising configuration parameters of a search space,the configuration parameters indicating one or more SBs on which thewireless device may monitor PDCCH candidates of the search space. Thewireless device may monitor PDCCH candidates associated with a searchspace on the one or more SBs based on the configuration parameters.

In existing technologies, a wireless device may index CCEs, from a firstinitial number (e.g., 0) to a second number (e.g., a maximum/totalnumber configured on a CORESET), of radio resources of a CORESET on aBWP (or a cell when BWP is not configured on the cell), as shown in FIG.25B. The CCEs are across frequency resources of the BWP. The wirelessdevice may monitor PDCCH candidates of a SS, for detecting a DCI, on oneor more CCEs of the CCEs. The wireless device may receive the DCI on atleast one CCE of the one or more CCEs. The wireless device may determinea starting CCE of the at least one CCE based on the CCE indexes, e.g.,the starting CCE having a lowest CCE index among the at least one CCE.The wireless device may determine a PUCCH resource for HARQ-ACK feedbackbased on at least one of: a CCE index of the starting CCE of the atleast one CCE on which the wireless device receives a DCI, the totalnumber of CCEs and a PRI of the DCI.

In a NR-U cell (or a BWP of the cell), a wireless device may monitor aSS (or monitor PDCCH candidates of the SS) on one or more SBs of theBWP. In an example, the wireless device may receive a DCI on one of theone or more SBs, based on a LBT procedure at the base station, when atmost one DCI is allowed to be transmitted for data scheduling in theBWP. The wireless device, by implementing existing technologies, maydetermine different PUCCH resources for UCI transmission when receivinga DCI on different SBs of the BWP. The wireless device, by implementingexisting technologies, may determine PUCCH resource for transmitting UCIsuch that the base station needs to allocate (or reserve) PUCCHresources more than the wireless device actually utilizes to transmitthe UCI. This may result in decreasing system throughput and/or reduceduplink resource utilization efficiency. The existing technologies mayresult in collision of UCI transmission on PUCCH (within the samewireless device, or among different wireless devices), decreasing systemthroughput, increasing uplink transmission latency, and/or increasingpower consumption. Therefore, there is a need to improve PUCCH resourceallocation method for a wideband NR-U to improve uplink resourceutilization efficiency, system throughput, reduce collision of UCItransmission, reduce power consumption, etc.

In one of example embodiments, a wireless device may index CCEs of aCORESET, for each RB set of a BWP, from a same initial value (e.g., 0).In an example, the wireless device may index CCEs of the CORESET in afirst RB set of the BWP from 0 to N−1, where N is a total number of CCEsof the CORESET in an RB set. The wireless device may index CCEs of theCORESET in a second RB set of the BWP from 0 to N−1. Based on indexingthe CCEs of the CORESET from a same initial value for different RB setsof the BWP, the wireless device may determine a PUCCH resource based on:a CCE index of a starting CCE of one or more CCEs on which the wirelessdevice receives a DCI, a PUCCH resource index indicated by the DCI, atotal number of CCEs of the CORESET. Based on the example embodiment,the wireless device may select/determine a same PUCCH resourceregardless of on which RB set the wireless device receives the DCI.Example embodiment may allow a base station to reduce PUCCH resourceallocation/reservation for the wireless device and therefore improveuplink resource utilization efficiency.

FIG. 28 shows an example embodiment of PUCCH resourceallocation/determination method for a wideband NR-U cell.

In an example, a base station may transmit a wireless device one or moreRRC messages comprising configuration parameter of a cell (e.g., PCell,or SCell). The cell may comprise a plurality of BWPs. The cell maycomprise a single BWP. In an example, a BWP may comprise a number (e.g.,4) of LBT SBs (SBs or RB sets which may be equally referred to as inthis specification), each SB occupying a number of RBs (or RB groups) ofthe BWP. As shown in FIG. 28 , the SBs of the BWP comprise SB 0, SB 1,SB 2, and so on. The configuration parameters may indicate a pluralityof CORESETs configured on a BWP. The configuration parameters mayindicate that frequency resources of a CORESET of the plurality ofCORESETs are confined in a bandwidth of a SB of the BWP. The frequencyresource mapping pattern (e.g., defining on which resource blocks of thefirst SB the CORESET comprises, as shown by frequencyDomainResources inFIG. 24 ) of the CORESET on the first SB is replicated to the rest SBsof the BWP. The configuration parameters may indicate a plurality of SSsare configured on a CORESET. For each SS of the plurality of SSs, theconfiguration parameters may comprise a monitoring frequency locationparameter (e.g., a bitmap, or a monitoring location indication, as shownin FIG. 28 ) indicating on which SB(s) a monitoring frequency locationof the SS is configured. As shown in FIG. 28 , the monitoring locationindication for a SS (e.g., SS_(i)) comprises a bit string “110 . . . ”,indicating monitoring frequency location comprising SB 0, SB 1. Inresponse to the monitoring frequency location comprising SB 0, SB 1, thewireless device may monitor SS_(i) on SB 0 and SB 1, and not monitorSS_(i) on the rest SBs (e.g., SB 2 and SB 3).

In an example, in response to monitoring SS_(i) on SB 0 and SB 1, thewireless device may attempt to detect DCI(s) on CCEs of SS_(i) on SB 0,and/or DCI(s) on CCEs of SS_(i) on SB1 (e.g., simultaneously, orsequentially). The wireless device may index CCEs, on different SBs ofthe BWP, from a same initial value (e.g., 0) to N−1 (e.g., N is a totalnumber of CCEs in a SB). Based on the indexing the CCEs, the wirelessdevice may attempt to detect first DCI on CCE 2, CCE 4, CCE 6, . . . onSB 0, and attempt to detect second DCI on CCE 2, CC 4, CCE 6, . . . onSB 1, where CC 2, CC 4, CC 6, . . . are determined for SS_(i) byimplementing examples of FIG. 25B.

In an example, the wireless device may receive a first DCI on CCEs ofSS_(i) on SB 0 of the BWP. The wireless device may receive a second DCIon CCEs of SS_(i) on SB 1 of the BWP. The wireless device may receivethe first DCI and/or the second DCI based on LBT procedure performed bya base station on SB 0 and SB 1. In an example, the base station maytransmit the first DCI on SB 0 when the base station determines achannel is clear on SB 0 based on a LBT procedure performed on SB 0. Thebase station may transmit the second DCI on SB 1 when the base stationdetermines a channel is clear on SB 1 based on a LBT procedure performedon SB 1. Based on the indexing CCEs, on different SBs, from a sameinitial value, the wireless device may determine a first starting CCE,on SB 0, on which the first DCI is received, may have a same CCE indexof a second starting CCE, on SB 1, on which the second DCI is received.The first DCI may indicate a same PRI value as the second DCI does.

In response to receiving a DCI (the first DCI or the second DCI), thewireless device may attempt to detect a TB based on downlink assignmentof the DCI. The wireless device may determine an acknowledgementinformation for reception of the TB based on the detecting the TB. In anexample, the wireless device may determine the acknowledgementinformation comprises a positive acknowledgment (ACK) for reception ofthe TB in response to the detecting the TB being successful. In anexample, the wireless device may determine the acknowledgementinformation comprises a negative acknowledgment (NACK) for reception ofthe TB in response to the detecting the TB not being successful.

In an example, the wireless device may determine a PUCCH resource fortransmitting the acknowledgement information, based on the starting CCE,a PRI of the DCI, by implementing example embodiment described abovewith respect to FIG. 25A and/or FIG. 25B. As shown in FIG. 28 , thestarting CCE may have a CCE index equal to 2, regardless of on which SBthe wireless device receives the DCI. By implementing exampleembodiment, the wireless device may determine the PUCCH resource, basedon the CCE index of the starting CCE, wherein CCEs within a SB areindexed from a same initial value for each SB of the BWP. The wirelessdevice may determine the PUCCH resource, based on the CCE index of thestaring CCE, regardless on which SB the wireless device receives the DCI(the first DCI or the second DCI). Otherwise, based on existingtechnologies, the wireless device may determine different starting CCEindex when receiving DCI on different SB, therefore the wireless devicemay determine different PUCCH resource for transmission of UCI based onthe different starting CCE index. Example embodiment may allow the basestation to reduce PUCCH resource allocation/reservation for the wirelessdevice and therefore improve uplink resource utilization efficiency.

In a NR-U cell (or a BWP of the cell), a wireless device may monitor aSS (or monitor PDCCH candidates of the SS) on one or more SBs of theBWP. The wireless device may receive multiple DCIs on multiple SBs ofthe one or more SBs, each DCI being received via a search space of aCORESET on a respective SB of the one or more SBs. The wireless devicemay receive multiple DCIs on the multiple SBs when the base stationsucceeds LBT procedure on the multiple SBs. Receiving multiple DCIs onmultiple SBs may increase system throughputs, e.g., when each DCIschedules a respective TB. The wireless device, based on existingtechnologies, may determine a same PUCCH resource for HARQ-ACKtransmissions for different TBs scheduled by the multiple DCIs. This mayresult in collision of HARQ-ACK transmissions for different TBs.Therefore, existing technologies may result in collision of UCItransmission on PUCCH (within the same wireless device, or amongdifferent wireless devices), decreasing system throughput, increasinguplink transmission latency, and/or increasing power consumption.Therefore, there is a need to improve PUCCH resource allocation methodfor a wideband NR-U to improve uplink resource utilization efficiency,system throughput, reduce collision of UCI transmission, reduce powerconsumption, etc.

FIG. 29 shows an example of PUCCH resource determination mechanism whenmultiple PDCCH monitoring frequency locations on multiple SBs of a BWPare supported. In an example, a base station may transmit a wirelessdevice one or more RRC messages comprising configuration parameter of acell (e.g., PCell, or SCell). The cell may comprise a plurality of BWPs.The cell may comprise a single BWP. In an example, a BWP may comprise anumber (e.g., 4) of SBs, each SB occupying a number of RBs (or RBgroups) of the BWP. As shown in FIG. 29 , the SBs of the BWP comprise SB0, SB 1, and so on. The configuration parameters may indicate aplurality of CORESETs configured on a BWP. The configuration parametersmay indicate that frequency resources of a CORESET are confined in abandwidth of a SB of the BWP. The configuration parameters may indicatea plurality of SSs are configured on a CORESET. For each SS of theplurality of SSs, the configuration parameters may comprise a monitoringfrequency location parameter (e.g., a bitmap, or a monitoring locationindication, as shown in FIG. 29 ) indicating on which SB(s) a monitoringfrequency location of the SS is configured. As shown in FIG. 29 , themonitoring location indication for a SS (e.g., SS_(i)) comprises a bitstring “110 . . . ”, indicating monitoring frequency location comprisingSB 0, SB 1, wherein each bit of the bit string indicates whether acorresponding SB shall be monitored by the wireless device for the SS.In response to the monitoring frequency location comprising SB 0, SB 1,the wireless device may monitor SS_(i) on SB 0 and SB 1, and not monitorSS_(i) on other SBs of the BWP.

In an example, a wireless device may index CCE of each CCE of a SB basedon at least one of: a SB index, and a total number of CCEs of a CORESET.In an example, a CORESET on SB 0 may comprise a same total number ofCCEs on SB 1. In the example of FIG. 29 , the total number of CCEs ofthe CORESET is N. The wireless device may index CCEs of the CORESET onSB 0 from CCE 0 (or CCE 1) to CCE N−1 (or CCE N). The wireless devicemay index an i-th CCE of CCEs of the CORESET on SB j as: N*(j−1)+i, wheni starts from 0. The wireless device may index an i-th CCE of CCEs ofthe CORESET on SB j as: N*(j−1)+i−1 when i starts from 1. In an example,an i-th CCE of CCEs on SB 0 and an i-th CCE of CCEs on SB j may havedifferent CCE indexes. Having different CCE indexes on different SBs mayallow a wireless device to reduce PUCCH resource collision.

In an example, a base station may transmit to a wireless device one ormore RRC messages comprising configuration parameters of a BWPcomprising a plurality of SBs, the configuration parameters indicating aCCE index offset (e.g., SB specific) for CCEs of a respective SB of theplurality of SBs. In an example, the configuration parameter mayindicate a 1st CCE_index_offset for a 1st SB, a 2nd CCE_index_offset for2nd SB, and so on. Based on the configuration parameters, the wirelessdevice may index an i-th CCE on 1st SB as 1st CCE_index_offset+i, indexan i-th CCE on 2nd SB as 2nd CCE_index_offset+i, and so on. The CCEindex offset for each SB may be a cell specific parameter, or a UEspecific parameter. The base station may transmit the CCE index offsetin a system information in response to the CCE index offset being a cellspecific parameter. The base station may transmit the CCE index offsetin a UE specific cell configuration message in response to the CCE indexoffset being a UE specific parameter.

As shown in FIG. 29 , the wireless device may attempt to detect DCI(s)on CCEs on SB 0 and SB 1. In an example, the wireless device may attemptto detect first DCI on CCE 2, CCE 4, CCE 6, . . . on SB 0, where CC 2,CC 4, CC 6, are determined for SS_(i) by implementing examples of FIG.25B. The wireless device, based on monitoring CCE 2, CCE 4, CCE 6 . . ., may attempt to detect second DCI on CCE N+2, CC N+4, CCE N+6, . . . onSB 1.

As shown in FIG. 29 , the wireless device may receive a first DCI onCCEs of SS_(i) on SB 0 of the BWP. The wireless device may receive asecond DCI on CCEs of SS_(i) on SB 1 of the BWP. A first starting CCE ofthe CCEs, on SB 0, on which the first DCI is received, may have a firstCCE index (e.g., 2 as shown in FIG. 29 ). A second starting CCE of theCCEs, on SB 1, on which the second DCI is received, may have a secondCCE index (e.g., N+2 as shown in FIG. 29 ). The first starting CCE andthe second starting CCE, at a same location in order of CCE indexes onSB 0 and SB 1, may have different CCE indexes. In an example, the firstDCI may indicate a same PRI value as the second DCI does.

In response to receiving the first DCI, the wireless device may attemptto detect a first TB based on first downlink assignment of the firstDCI. The wireless device may determine a first acknowledgementinformation for reception of the first TB based on the detecting thefirst TB. In an example, the wireless device may determine the firstacknowledgement information comprises a positive acknowledgment (ACK)for reception of the first TB in response to the detecting the first TBbeing successful. In an example, the wireless device may determine thefirst acknowledgement information comprises a negative acknowledgment(NACK) for reception of the first TB in response to the detecting thefirst TB not being successful.

In response to receiving the second DCI, the wireless device may attemptto detect a second TB (or the first TB in case of repetition) based onsecond downlink assignment of the second DCI. The wireless device maydetermine a second acknowledgement information for reception of thesecond TB based on the detecting the second TB. In an example, thewireless device may determine the second acknowledgement informationcomprises an ACK for reception of the second TB in response to thedetecting the second TB being successful. In an example, the wirelessdevice may determine the second acknowledgement information comprises aNACK for reception of the second TB in response to the detecting thesecond TB not being successful.

In an example, the wireless device may determine a first PUCCH resourcefor transmitting the first acknowledgement information, based on thefirst starting CCE, a first PRI of the first DCI. The wireless devicemay determine a second PUCCH resource for transmitting the secondacknowledgement information, based on the second starting CCE, a secondPRI of the first DCI.

In an example, when a wireless device does not have dedicated PUCCHresource configuration, the wireless device may determine the firstPUCCH resource, r_(PUCCH), based on the first starting CCE, a first PRIof the first DCI, as

${r_{PUCCH} = {\left\lfloor \frac{2 \cdot n_{{CCE},0}}{N_{CCE}^{\prime}} \right\rfloor + {2 \cdot \Delta_{PRI}}}},$where N′_(CCE)=K*N_(CCE), N_(CCE) is a total number of CCEs in a CORESETon SB 0, K is a total number of SBs the wireless device is configured tomonitor, n_(CCE,0) is a CCE index of a first starting CCE for receivingthe first DCI on SB 0, and Δ_(PRI) is a value of the PRI field in thefirst DCI. In an example, K may be a maximum number of SBs configured onthe BWP, or a predefined value (e.g., 4). As shown in FIG. 29 , thewireless device may determine the first PUCCH resource as PUCCH resource2.

As shown in FIG. 29 , the wireless device may determine the second PUCCHresource, r_(PUCCH), based on the second starting CCE, a second PRI ofthe second DCI, as

${r_{PUCCH} = {\left\lfloor \frac{2 \cdot n_{{CCE},0}}{N_{CCE}^{\prime}} \right\rfloor + {2 \cdot \Delta_{PRI}}}},$where N′_(CCE)=K*N_(CCE), N_(CCE) is a total number of CCEs in a CORESETon SB 1, K is a total number of SBs the wireless device is configured tomonitor, n_(CCE,0) is a CCE index of a second starting CCE for receivingthe second DCI on SB 1, and Δ_(PRI) is a value of the PRI field in thesecond DCI. As shown in FIG. 29 , the wireless device may determine thesecond PUCCH resource as PUCCH resource 3.

In an example, when a wireless device has dedicated PUCCH resourceconfiguration, the wireless device may determine the first PUCCHresource, r_(PUCCH) (e.g., 0≤r_(PUCCH)≤R_(PUCCH)−1), from a set of PUCCHresources (e.g., the first set when configured with multiple sets ofPUCCH resources), based on the first starting CCE, a first PRI of thefirst DCI, as

$r_{PUCCH} = {{\left\lfloor \frac{n_{{CCE},p} \cdot \left\lfloor {R_{PUCCH}/8} \right\rfloor}{N_{{CCE},p}^{\prime}} \right\rfloor + {\Delta_{PRI} \cdot \left\lfloor \frac{R_{PUCCH}}{8} \right\rfloor} + {R_{PUCCH}{mod}8{if}{}\Delta_{PRI}}} \geq {R_{PUCCH}{mod}8}}$if Δ_(PRI)≥R_(PUCCH) mod 8 where N′_(CCE,p)=K*N_(CCE,p), N_(CCE,p) is atotal number of CCEs in CORESET p on SB 0, K is a total number of SBsthe wireless device is configured to monitor, n_(CCE,p) is a CCE indexof the first starting CCE in CORESET p for receiving the first DCI on SB0, and Δ_(PRI) is a value of the PRI field in the first DCI. As shown inFIG. 29 , the wireless device may determine the first PUCCH resource asPUCCH resource 2.

In an example, the wireless device may determine the second PUCCHresource, r_(PUCCH) (e.g., 0≤r_(PUCCH)≤R_(PUCCH)−1) based on the secondstarting CCE, a second PRI of the second DCI, as

$r_{PUCCH} = {{\left\lfloor \frac{n_{{CCE},p} \cdot \left\lfloor {R_{PUCCH}/8} \right\rfloor}{N_{{CCE},p}^{\prime}} \right\rfloor + {\Delta_{PRI} \cdot \left\lfloor \frac{R_{PUCCH}}{8} \right\rfloor} + {R_{PUCCH}{mod}8{if}\Delta_{PRI}}} \geq {R_{PUCCH}{mod}8}}$if Δ_(PRI)≥R_(PUCCH) mod 8 where N′_(CCE,p)=K*N_(CCE,p), N_(CCE,p) is atotal number of CCEs in CORESET p on SB 1, K is a total number of SBsthe wireless device is configured to monitor, n_(CCE,p) is a CCE indexof the second starting CCE in CORESET p for receiving the second DCI onSB 1, and Δ_(PRI) is a value of the PRI field in the second DCI. Asshown in FIG. 29 , the wireless device may determine the second PUCCHresource as PUCCH resource 3.

As shown in FIG. 29 , the wireless device may determine different PUCCHresources for ACK/NACK transmission for different TBs. By exampleembodiments, the wireless device may reduce PUCCH transmissioncollision, and improve uplink transmission latency, system throughput.

In an example, the wireless device may index CCEs of a SB of a pluralityof SBs on a BWP independently and separately. The CCE indexes may bereused on different SBs. In an example, the wireless device may indexCCEs of a first SB from CCE 0 to CCE N−1, and index CCEs of a second SBfrom CCE 0 to CCE N−1. Reusing CCE indexes on different SBs may improveUE's implementation complexity, and/or backward compatibility.

In an example, when the wireless device reuses CCE indexes on differentSBs, the wireless device may determine a PUCCH resource, r_(PUCCH),based on a starting CCE, a SB index of a SB (e.g., SB 0 or SB 1), a PRIof a DCI received on the SB, as

${r_{PUCCH} = {\left\lfloor \frac{{2 \cdot n_{{CCE},0}} + {{SB\_ index} \star N_{CCE}}}{N_{CCE}^{\prime}} \right\rfloor + {2 \cdot \Delta_{PRI}}}},$where N′_(CCE)=K*N_(CCE), N_(CCE) is a total number of CCEs in a CORESETon the SB, K is a total number of SBs the wireless device is configuredto monitor, n_(CCE,0) is a CCE index of the starting CCE for receivingthe DCI on the SB, SB_index is a SB index of the SB on which thewireless device receives the DCI, and Δ_(PRI) is a value of the PRIfield in the DCI.

In an example, when the wireless device reuses CCE indexes on differentSBs, the wireless device may determine a PUCCH resource, r_(PUCCH)(e.g., 0≤r_(PUCCH)≤R_(PUCCH)−1), from a set of PUCCH resources (e.g.,the first set when configured with multiple sets of PUCCH resources),based on a starting CCE, a SB index of a SB (e.g., SB 0 or SB 1), and/ora PRI of a DCI received on the SB. In an example, the wireless devicemay determine r_(PUCCH) as

$r_{PUCCH} = {{{SB\_ index} + \left\lfloor \frac{n_{{CCE},p} \cdot \left\lfloor {R_{PUCCH}/8} \right\rfloor}{N_{{CCE},p}^{\prime}} \right\rfloor + {\Delta_{PRI} \cdot \left\lfloor \frac{R_{PUCCH}}{8} \right\rfloor} + {R_{PUCCH}{mod}8{if}\Delta_{PRI}}} \geq {R_{PUCCH}{mod}8}}$

where N′_(CCE,p)=K*N_(CCE,p), N_(CCE,p) is a total number of CCEs inCORESET p on the SB, K is a total number of SBs the wireless device isconfigured to monitor, n_(CCE,p) is a CCE index of the starting CCE inCORESET p for receiving the DCI on the SB, SB_index is a SB index of theSB on which the wireless device receives the DCI, and Δ_(PRI) is a valueof the PRI field in the DCI. In an example, when the total number of SBsare greater than 2, SB_index may be modeled by

$\left\lfloor \frac{R_{PUCCH}}{8} \right\rfloor.$

FIG. 30 shows an example flowchart of PUCCH resource determinationmechanism. In an example, a base station may transmit to a wirelessdevice one or more RRC messages comprising configuration parameters of acell (not shown in FIG. 30 ). The cell may comprise a plurality of BWPs.A BWP, of the plurality of BWPs, may comprise a plurality of SBs. In anexample, the base station may transmit to a wireless device a command(e.g., a DCI) indicating an activation of a BWP. In response toreceiving the command, the wireless device may activate the BWP. Thewireless device may, in response to activating the BWP, monitor a SS ofa CORESET on a first SB and a second SB, monitoring the first SB and thesecond SB being indicated in the configuration parameters. The basestation may perform LBT procedure on the first SB and the second SBsequentially or simultaneously.

In an example, the base station may determine LBT procedure on the firstSB indicates a clear channel on the first SB. In response to LBTprocedure indicating a clear channel on the first SB, the base stationmay transmit to the wireless device a first DCI via the first SB, thefirst DCI indicating a first downlink radio resource for downlinkassignment for transmission of a first TB and a first PUCCH resource forACK/NACK transmission for the first TB. In an example, the base stationmay determine LBT procedure on the second SB indicates a clear channelon the second SB. In response to LBT procedure indicating a clearchannel on the second SB, the base station may transmit to the wirelessdevice a second DCI via the second SB, the second DCI indicating asecond downlink radio resource for downlink assignment for transmissionof a second TB (or the first TB in case of repetition) and a secondPUCCH resource for ACK/NACK transmission for the second TB.

In an example, the wireless device may receive the first DCI duringmonitoring the SS of the CORESET on the first SB, and receive the secondDCI during monitoring the SS of the COREST on the second SB. Thewireless device may, based on receiving the first DCI, detect the firstTB via the first downlink radio resource on the first SB, and determinea first acknowledgement information for detection of the first TB. Thewireless device may, based on receiving the second DCI, detect thesecond TB via the second downlink radio resource on the second SB, anddetermine a second acknowledgement information for detection of thesecond TB.

In an example, the wireless device may determine a first PUCCH resource,for transmission of the first acknowledgement information, based on: afirst CCE index of a starting CCE of CCEs of the CORESET for receivingthe first DCI, a SB index of the first SB, and/or a PRI value indicatedin the first DCI. In an example, the wireless device may determine asecond PUCCH resource, for transmission of the second acknowledgementinformation, based on: a second CCE index of a starting CCE of CCEs ofthe CORESET for receiving the second DCI, a SB index of the second SB,and/or a PRI value indicated in the second DCI. The wireless device maydetermine the first PUCCH resource and/or the second PUCCH resource byimplementing examples of FIG. 29 . The wireless device my transmit thefirst acknowledgement for reception of the first TB via the first PUCCHresource. The wireless device may transmit the second acknowledgementfor reception of the second TB via the second PUCCH resource.

FIG. 31 shows an example of PUCCH configuration when multiple SBs aresupported in a NR-U system. In an example, a base station may transmit awireless device one or more RRC messages comprising configurationparameter of a cell (e.g., PCell, or SCell). The cell may comprise aplurality of BWPs. The cell may comprise a single BWP. In an example, aBWP may comprise a number (e.g., 4) of SBs, each SB occupying a numberof RBs (or RB groups) of the BWP. As shown in FIG. 31 , the SBs of theBWP comprise SB 0, SB 1, SB 2, and so on. The configuration parametersmay indicate a plurality of CORESETs configured on a BWP. Theconfiguration parameters may indicate that frequency resources of aCORESET are confined in a bandwidth of a SB of the BWP. Theconfiguration parameters may indicate a plurality of SSs are configuredon a CORESET. For each SS of the plurality of SSs, the configurationparameters may comprise a monitoring frequency location parameter (e.g.,a bitmap, or a monitoring location indication, as shown in FIG. 31 )indicating on which SB(s) a monitoring frequency location of the SS isconfigured. As shown in FIG. 31 , the monitoring location indication fora SS (e.g., SS_(i)) comprises a bit string “110 . . . ”, indicatingmonitoring frequency location comprising SB 0, SB 1. In response to themonitoring frequency location comprising SB 0, SB 1, the wireless devicemay monitor SS_(i) on SB 0 and SB 1, and not monitor SS_(i) on other SBsof the BWP.

In an example, the wireless device may index CCEs of a SB of a pluralityof SBs on a BWP independently and separately. The CCE indexes may bereused on different SBs. In an example, the wireless device may indexCCEs of a first SB (e.g., SB 0) from CCE 0 to CCE N−1, and index CCEs ofa second SB (e.g., SB 1) from CCE 0 to CCE N−1. Reusing CCE indexes ondifferent SBs may improve UE's implementation complexity, and/orbackward compatibility.

In an example, a base station may transmit to a wireless device one ormore RRC messages comprising configuration parameters of PUCCH resourceconfiguration on a first BWP on a PCell or a PUCCH SCell. In an example,the configuration parameters of the PUCCH resource configuration mayindicating a plurality of PUCCH resource sets. Each PUCCH resource setof the plurality of PUCCH resource sets may comprise a number of PUCCHresources. In an example, the configuration parameters may indicate afirst subset of the number of PUCCH resources, of a PUCCH resource set,correspond to a first SB of a plurality of SBs of a BWP of a cell (e.g.,PCell or SCell), a second subset of the number of PUCCH resourcescorrespond to a second SB of the plurality of SBs of the BWP of thecell, and so on. As shown in FIG. 31 , PUCCH resources of a PUCCHresource set may comprise PUCCH resources with PUCCH resource index 0,1, 2, 3, 4, . . . , K−1, K+1 . . . , and M. K may be a total number ofPUCCH resources for a first SB. M may be a total number of the PUCCHresources in the PUCCH resource set. K and/or M may be indicated in theone or more RRC messages. In an example, the configuration parametersmay indicate PUCCH resources with PUCCH resource index 0, 1, . . . K−1correspond to (or are associated with) the first SB. The configurationparameters may indicate PUCCH resources with PUCCH resource index K,K+1, . . . 2K−1 correspond to (or are associated with) the second SB. Inan example, the total number of PUCCH resources (e.g., K) for the firstSB may be different from the total number (e.g., J) of PUCCH resourcesfor the second SB, where K and J are indicated in the one or more RRCmessages or are set to predefined values (e.g., 8, 16, 32, and anynumber greater than zero).

In an example, a base station may transmit to a wireless device one ormore RRC messages comprising configuration parameters of PUCCH resourceconfiguration on a first BWP on a PCell or a PUCCH SCell. In an example,the configuration parameters of the PUCCH resource configuration mayindicating a plurality of PUCCH resource sets. Each PUCCH resource setof the plurality of PUCCH resource sets may comprise a number of PUCCHresources. In an example, the configuration parameters may indicate afirst PUCCH resource index offset corresponds to a first SB of aplurality of SBs of a BWP of a cell (e.g., PCell or SCell), a secondPUCCH resource index offset corresponds to a second SB of the pluralityof SBs of the BWP of the cell, and so on. In an example, based onreceiving the one or more RRC messages, the wireless device maydetermine a first PUCCH resource, for the first acknowledgementinformation for reception of the first TB via the first SB, based on atleast one of: the first PUCCH resource index offset, a CCE index of astarting CCE for receiving the first DCI, a PRI value indicated in thefirst DCI. In an example, based on receiving the one or more RRCmessages, the wireless device may determine a second PUCCH resource, forthe second acknowledgement information for reception of the second TBvia the second SB, based on at least one of: the second PUCCH resourceindex offset, a CCE index of a starting CCE for receiving the secondDCI, a PRI value indicated in the second DCI.

As shown in FIG. 31 , the wireless device may attempt to detect DCI(s)on CCEs on SB 0 and SB 1. In an example, the wireless device may attemptto detect first DCI on CCE 2, CCE 4, CCE 6, . . . on SB 0, where CC 2,CC 4, CC 6, are determined for SS_(i) by implementing examples of FIG.25B. The wireless device, based on monitoring CCE 2, CCE 4, CCE 6 . . ., may attempt to detect second DCI on CCE 2, CC 4, CCE 6, . . . on SB 1.

As shown in FIG. 31 , the wireless device may receive a first DCI onCCEs of SS_(i) on SB 0 of the BWP. The wireless device may receive asecond DCI on CCEs of SS_(i) on SB 1 of the BWP. A first starting CCE ofthe CCEs, on SB 0, on which the first DCI is received, may have a sameCCE index (e.g., 2 as shown in FIG. 31 ) as a second starting CCE of theCCEs, on SB 1, on which the second DCI is received. A first starting CCEof the CCEs, on SB 0, on which the first DCI is received, may have adifferent CCE index from a second starting CCE of the CCEs, on SB 1, onwhich the second DCI is received. In an example, the first DCI mayindicate a same PRI value as the second DCI does.

In an example, the wireless device may, based on receiving the firstDCI, detect the first TB via the first downlink radio resource on thefirst SB, and determine a first acknowledgement information fordetection of the first TB. The wireless device may, based on receivingthe second DCI, detect the second TB via the second downlink radioresource on the second SB, and determine a second acknowledgementinformation for detection of the second TB.

In an example, the wireless device may determine a first PUCCH resource,from a first subset of PUCCH resources (e.g., PUCCH resources with PUCCHresource indexes 0, 1, 2, . . . K−1 as shown in FIG. 31 ), correspondingto the first SB, of the PUCCH resource set, for transmitting the firstacknowledgement information, based on the first starting CCE, a firstPRI of the first DCI. The wireless device may determine a second PUCCHresource, from a second subset of PUCCH resources (e.g., PUCCH resourceswith PUCCH resource indexes K, K+1, K+2, . . . 2*K−1 as shown in FIG. 31), corresponding to the second SB, of the PUCCH resource set, fortransmitting the second acknowledgement information, based on the secondstarting CCE, a second PRI of the first DCI. The wireless device maydetermine the first PUCCH resource from the first subset of PUCCHresources by implementing example embodiments of FIG. 25B. The wirelessdevice may determine the second PUCCH resource from the second subset ofPUCCH resources by implementing example embodiments of FIG. 25B.

As shown in FIG. 31 , the wireless device may determine different PUCCHresources, from different PUCH resource subsets corresponding todifferent SBs, for ACK/NACK transmission for different TBs. By exampleembodiments, the wireless device may reduce PUCCH transmissioncollision, and improve uplink transmission latency, system throughput.

Example embodiments of FIG. 28 , FIG. 29 and/or FIG. 31 may beimplemented based on configuration. In an example, when a wirelessdevice and a base station supports at most one DCI for data schedulingon multiple RB sets of a BWP, the base station and the wireless devicemay perform PUCCH resource determination method based on example of FIG.28 . When a wireless device and a base station supports multiple DCIsfor data scheduling on multiple RB sets of a BWP and uplink channel isheavily loaded, the base station and the wireless device may performPUCCH resource determination method based on example of FIG. 29 . When awireless device and a base station supports multiple DCIs for datascheduling on multiple RB sets of a BWP and uplink channel is notheavily loaded, the base station and the wireless device may performPUCCH resource determination method based on example of FIG. 31 .

In an example, a first DL SB of a plurality of DL SBs may be linked to afirst UL SB of a plurality of UL SBs. The plurality of DL SBs may becomprised in a DL BWP of a cell. The plurality of UL SBs may becomprised in an UL BWP of the cell. In an example, a wireless device mayreceive a DCI via a first DL SB of the plurality of DL SBs. The wirelessdevice may, based on linkage between the first DL SB and the first ULSB, determine a PUCCH resource on the first UL SB, for ACK/NACKtransmission.

In an example, a first wireless device may select a first UL SB from aplurality of UL SBs of a BWP for PUCCH transmission of ACK/NACK, basedon a selection priority. The selection priority may be indicated by anRRC message. The selection priority may be predefined. The selectionpriority may indicate an order of UL SB selection from the plurality ofUL SBs. In an example, different UEs may be configured with differentselection priorities. Configuring different selection priorities mayimprove PUCCH collisions.

In an example, a wireless device may monitor a PDCCH on CCEs of a SB ofa plurality of SBs of a BWP of a cell. The wireless device may receive,via the PDCCH on one or more CCEs of the CCEs, a DCI comprising a radioresource indication and a PUCCH resource index. The wireless device mayreceive a TB via a radio resource indicated by the radio resourceindication. The wireless device may determine a PUCCH resource based onat least one of: the PUCCH resource index, a SB index of the SB, and/ora CCE index of a starting CCE of the one or more of the CCEs. Thewireless device may transmit, via the PUCCH resource, an acknowledgementinformation for reception of the TB. The wireless device may furtherreceive one or more RRC messages comprising configuration parameters ofa cell comprising a plurality of BWPs, each of the plurality of BWPscomprising a plurality of SBs. Each of the plurality of SBs may beidentified with a respective SB index. The configuration parameters ofthe cell may further comprise first configuration parameters of a BWP ofthe plurality of BWPs, the first configuration parameters comprising oneor more radio resource configuration parameters of a CORESET. The one ormore radio resource configuration parameters of the CORESET may indicatethat frequency resources of the CORESET are confined in a bandwidth of aSB of the BWP. The one or more radio resource configuration parametersmay indicate that a search space, associated with the CORESET, isconfigured with one or more monitoring frequency location indication.Each frequency location indication, corresponding to a respective SB ofone or more SBs of the plurality of SBs, may indicate whether thewireless device monitors PDCCH for the search space on the SB. Thefrequency resources of the CORESET on a SB may comprise a plurality ofCCEs, each of the plurality of CCEs being identified with a CCE index.CCE index of a first CCE of the plurality of CCE may start from a firstpredefined value (e.g., 0, or 1).

In an example, the wireless device may monitor a PDCCH on the searchspace on a SB of the plurality of SBs, in response to a monitoringfrequency location indication, corresponding to the SB, indicating PDCCHmonitoring on the SB for the search space.

In an example, the one or more RRC messages may further indicate aplurality of PUCCH resource sets, each of the PUCCH resource setcomprising a plurality of PUCCH resources. Each of the plurality ofPUCCH resources may be identified with a respective PUCCH resourceindex. The wireless device may determine the PUCCH resource from theplurality of PUCCH resources of one of the plurality of PUCCH resourcesets.

In an example, the acknowledgement information may comprise a positiveacknowledgement (ACK) in response to reception of the TB beingsuccessful. The acknowledgement information may comprise a negativeacknowledgement (NACK) in response to reception of the TB not beingsuccessful.

In an example, the wireless device may monitor a second PDCCH on CCEs ofa second SB of the plurality of SB. The wireless device may receive, viathe second PDCCH on one or more CCEs of the CCEs, a second DCIcomprising a second radio resource indication and a second PUCCHresource index. The wireless device may receive a second TB via a secondradio resource indicated by the second radio resource indication. Thewireless device may determine a second PUCCH resource based on at leastone of: the second PUCCH resource index, a second SB index of the secondSB, and/or a second CCE index of a second starting CCE of the one ormore of the CCEs. The wireless device may transmit, via the second PUCCHresource, a second acknowledgement information for reception of thesecond TB.

In an example, the second PUCCH resource may be different from the PUCCHresource. The second SB index may be different from the SB index.

In an example, a wireless device may monitor a PDCCH on CCEs of a SB ofa plurality of SBs. The wireless device may receive, via the PDCCH onone or more CCEs of the CCEs, a DCI comprising a radio resourceindication and a PUCCH resource index. The wireless device may receive aTB via a radio resource indicated by the radio resource indication. Thewireless device may determine a PUCCH resource based on at least one of:the PUCCH resource index, a PUCCH resource index offset associated withthe SB, and/or a CCE index of a starting CCE of the one or more of theCCEs. The wireless device may transmit, via the PUCCH resource, anacknowledgement information for reception of the TB.

In an example, a wireless device may receive configuration parametersindicating a respective CCE index offset for a corresponding SB of aplurality of SBs. The wireless device may monitor a PDCCH on CCEs of aSB of a plurality of SBs. The wireless device may receive, via the PDCCHon one or more CCEs of the CCEs, a DCI comprising a radio resourceindication and a PUCCH resource index. The wireless device may receive aTB via a radio resource indicated by the radio resource indication. Thewireless device may determine a PUCCH resource based on at least one of:the PUCCH resource index, a respective CCE index offset corresponding tothe SB, and a CCE index of a starting CCE of the one or more of theCCEs. The wireless device may transmit, via the PUCCH resource, anacknowledgement information for reception of the TB.

FIG. 32 shows a flow diagram as per an aspect of an example embodimentof the present disclosure. At 3210, a wireless device may receiveconfiguration parameters of a BWP comprising RB sets, wherein CCEs of aCORESET of the BWP are across the RB sets and a subset of the CCEs,within each RB set of the RB sets, are indexed from a same initialvalue. At 3220, the wireless device may receive a DCI via one or moreCCEs of the subset of the CCEs within an RB set of the RB sets. At 3230,the wireless device may determine, a CCE index of a starting CCE of theone or more CCEs, based on indexing the subset of the CCEs from theinitial value within the RB set. At 3240, the wireless device maytransmit an uplink signal via an uplink resource determined based on theCCE index.

FIG. 33 shows a flow diagram as per an aspect of an example embodimentof the present disclosure. At 3310, a wireless device may receiveconfiguration parameters of a BWP comprising RB sets, wherein CCEs areacross the RB sets and a subset of the CCEs, within each RB set of theRB sets, are indexed from a same initial value. At 3320, the wirelessdevice may receive a control information via one or more CCEs of thesubset of the CCEs within an RB set of the RB sets. At 3330, thewireless device may transmit an uplink signal via an uplink resourcebased on an index of a CCE of the one or more CCEs.

According to an example embodiment, the wireless device may receive oneor more RRC messages comprising second configuration parameters of acell, wherein the cell comprises a plurality of bandwidth partscomprising the bandwidth part.

According to an example embodiment, the initial value may be zero. Thecontrol information may a DCI via a PDCCH on the one or more CCEs.

According to an example embodiment, each CCE of the CCEs may comprise anumber of resource element groups, wherein a resource-element groupcomprises an RB in a symbol.

According to an example embodiment, each RB set of the RB sets maycomprise one or more RBs of the bandwidth part. Each RB of the one ormore RBs may comprise a number of resource elements of the bandwidthpart. The first RB set may comprise one or more RBs non-overlapping witha second RB set of the RB sets.

According to an example embodiment, the configuration parameters mayindicate that a control resource set of the bandwidth part comprises theCCEs. The configuration parameters may indicate that a frequency domainresource allocation pattern of the control resource set is replicatedfor each RB set of the RB sets of the bandwidth part, wherein physicalradio resources of the CCEs of the control resource set are mapped toeach RB set. The wireless device may determine the uplink resourcefurther based on a total number of the first subset of the CCEs, withinthe first RB set, associated with the control resource set.

According to an example embodiment, the configuration parameters mayindicate one or more RB sets comprising the first RB set, from the RBsets of the bandwidth part, for a search space associated with thecontrol resource set. The search space may comprise the one or more CCEsof the first subset of the CCEs associated with the control resource setwithin the first RB set. The search space, associated with the controlresource set, may be configured with one or more monitoring frequencylocation indications, each frequency location indication correspondingto a respective RB set of the RB sets of the bandwidth part. Thewireless device may monitor a downlink control channel on the searchspace on the first RB set, in response to a monitoring frequencylocation indication, corresponding to the first RB set, indicatingdownlink control channel monitoring on the first RB set. The wirelessdevice may receive the control information during the monitoring thedownlink control channel on the search space.

According to an example embodiment, the uplink resource may comprise aphysical uplink control channel (PUCCH) resource.

According to an example embodiment, the configuration parameters mayindicate a plurality of PUCCH resources. Each of the plurality of PUCCHresources may be identified with a respective PUCCH resource index. Eachof the plurality of PUCCH resources may be associated with an RB setindex of an RB set of the RB sets. The wireless device may transmit thesignal via the uplink resource associated with the first RB set. Thecontrol information may comprise a PUCCH resource indication fieldindicating a PUCCH resource index. The wireless device may determine theuplink resource further based on the PUCCH resource index indicated bythe control information.

According to an example embodiment, the wireless device may determinethe uplink resource based on a PUCCH resource index indicated by thecontrol information and a PUCCH resource index offset determined basedon the index of the CCE.

According to an example embodiment, the control information may comprisedownlink assignment of downlink radio resource for transmitting atransport block. The wireless device may receive the transport block viathe downlink radio resource based on the control information.

According to an example embodiment, the signal may comprise anacknowledgement information corresponding to a transport block scheduledby the control information. The acknowledgement information may comprisea positive acknowledgement (ACK) in response to reception of thetransport block being successful. The acknowledgement information maycomprise a negative acknowledgement (NACK) in response to reception ofthe transport block not being successful.

According to an example embodiment, the CCE may be a starting CCE (e.g.,with the lowest CCE index) of the one or more CCEs based on indexing thefirst subset of the CCEs from the initial value within the first RB set.The wireless device may determine the uplink resource based on a PUCCHresource indicator in the downlink control information and a PUCCHresource offset determined based on the index of the starting CCE.

FIG. 34 shows a flow diagram as per an aspect of an example embodimentof the present disclosure. At 3410, a wireless device may monitor adownlink control channel on control channel elements (CCEs) of aresource block (RB) set of RB sets of a bandwidth part. At 3420, thewireless device may receive, on one or more CCEs of the CCEs, a downlinkcontrol information comprising a physical uplink control channel (PUCCH)resource index. At 3430, the wireless device may transmit an uplinksignal via a PUCCH resource determined based on the PUCCH resourceindex, an RB set index of the RB set and a CCE index of a starting CCEof the one or more CCEs.

What is claimed is:
 1. A method comprising: receiving, by a wirelessdevice, configuration parameters of a control resource set in abandwidth part (BWP), wherein: the control resource set comprisescontrol channel elements (CCEs) across a first resource block (RB) setof the BWP and a second RB set of the BWP; the first RB set comprises afirst subset of the CCEs, wherein first index values of the first subsetstart from a first initial value; and the second RB set comprises asecond subset of the CCEs, wherein second index values of the secondsubset start from a second initial value that is the same as the firstinitial value; receiving a control information via one or more CCEs ofthe first subset; and transmitting a signal via an uplink resource basedon an index of a CCE of the one or more CCEs of the first subset,wherein the index is determined based on the first index values of thefirst subset starting from the first initial value that is the same asthe second initial value.
 2. The method of claim 1, wherein the firstinitial value and the second initial value are each zero, and whereinthe first indexes of the first subset and the second indexes of thesecond subset are each in an ascending order.
 3. The method of claim 1,wherein the configuration parameters further indicate that a frequencydomain resource allocation pattern of the control resource set isreplicated for each of the first RB set and the second RB set, andwherein physical radio resources of the CCEs of the control resource setare mapped to the first RB set and the second RB set.
 4. The method ofclaim 3, wherein the uplink resource is determined further based on atotal number of the first subset of the CCEs, within the first RB set,associated with the control resource set.
 5. The method of claim 1,wherein the configuration parameters indicate one or more RB sets,comprising the first RB set, for a search space associated with thecontrol resource set.
 6. The method of claim 5, wherein the search spacecomprises the one or more CCEs of the first subset of the CCEsassociated with the control resource set within the first RB set.
 7. Themethod claim 5, wherein the search space, associated with the controlresource set, is configured with one or more monitoring frequencylocation indications, each frequency location indication correspondingto a respective RB set of RB sets of the BWP, wherein the RB setscomprise the first RB set and the second RB set.
 8. The method of claim1, wherein the uplink resource is determined based on: a physical uplinkcontrol channel (PUCCH) resource index indicated by the controlinformation; and a PUCCH resource index offset determined based on theindex of the CCE.
 9. The method of claim 1, wherein the CCE is astarting CCE of the one or more CCEs.
 10. The method of claim 1, furthercomprising: receiving a second control information via one or moresecond CCEs of the second subset, of the CCEs, within the second RB set;and transmitting a second signal via a second uplink resource based on asecond index of a CCE of the one or more second CCEs of the secondsubset, wherein the second index is determined based on the second indexvalues of the second subset starting from the second initial value thatis the same as the first initial value.
 11. A wireless devicecomprising: one or more processors; and memory storing instructionsthat, when executed by the one or more processors, cause the wirelessdevice to: receive configuration parameters of a control resource set ina bandwidth part (BWP), wherein: the control resource set comprisescontrol channel elements (CCEs) across a first resource block (RB) setof the BWP and a second RB set of the BWP; the first RB set comprises afirst subset of the CCEs, wherein first index values of the first subsetstart from a first initial value; and the second RB set comprises asecond subset of the CCEs, wherein second index values of the secondsubset start from a second initial value that is the same as the firstinitial value; receive a control information via one or more CCEs of thefirst subset; and transmit a signal via an uplink resource based on anindex of a CCE of the one or more CCEs of the first subset, wherein theindex is determined based on the first index values of the first subsetstarting from the first initial value that is the same as the secondinitial.
 12. The wireless device of claim 11, wherein the first initialvalue and the second initial value are each zero, and wherein the firstindexes of the first subset and the second indexes of the second subsetare each in an ascending order.
 13. The wireless device of claim 11,wherein the configuration parameters further indicate that a frequencydomain resource allocation pattern of the control resource set isreplicated for each of the first RB set and the second RB set, andwherein physical radio resources of the CCEs of the control resource setare mapped to the first RB set and the second RB set.
 14. The wirelessdevice of claim 11, wherein the configuration parameters indicate one ormore RB sets comprising the first RB set, for a search space associatedwith the control resource set.
 15. The wireless device of claim 14,wherein the search space comprises the one or more CCEs of the firstsubset of the CCEs associated with the control resource set within thefirst RB set.
 16. The wireless device claim 14, wherein the searchspace, associated with the control resource set, is configured with oneor more monitoring frequency location indications, each frequencylocation indication corresponding to a respective RB set of RB sets ofthe BWP, wherein the RB sets comprise the first RB set and the second RBset.
 17. The wireless device of claim 11, wherein the uplink resource isdetermined based on: a physical uplink control channel (PUCCH) resourceindex indicated by the control information; and a PUCCH resource indexoffset determined based on the index of the CCE.
 18. The wireless deviceof claim 11, wherein the CCE is a starting CCE of the one or more CCEs.19. The wireless device of claim 11, wherein the instructions furthercause the wireless device to: receive a second control information viaone or more second CCEs of the second subset, of the CCEs, within thesecond RB set; and transmit a second signal via a second uplink resourcebased on a second index of a CCE of the one or more second CCEs of thesecond subset, wherein the second index is determined based on thesecond index values of the second subset starting from the secondinitial value that is the same as the first initial value.
 20. A systemcomprising: a base station comprising: one or more first processors andfirst memory storing first instructions that, when executed by the oneor more first processors, cause the base station to: transmitconfiguration parameters of a control resource set in a bandwidth part(BWP), wherein: the control resource set comprises control channelelements (CCEs) across a first resource block (RB) set of the BWP and asecond RB set of the BWP; the first RB set comprises a first subset ofthe CCEs, wherein first index values of the first subset start from afirst initial value; and the second RB set comprises a second subset ofthe CCEs, wherein second index values of the second subset start from asecond initial value that is the same as the first initial value;transmit a control information via one or more CCEs of the first subset;and a wireless device comprising: one or more second processors andsecond memory storing second instructions that, when executed by the oneor more second processors, cause the wireless device to: receive theconfiguration parameters; receive the control information; and transmita signal via an uplink resource based on an index of a CCE of the one ormore CCEs of the first subset, wherein the index is determined based onthe first index values of the first subset starting from the firstinitial value that is the same as the second initial.